22ea809c67
Summary: When running tck tests there was a peculiar behavior where sometimes some queries worked, and sometimes they failed. Nothing was failing when memgraph was restarted between each query (scenario) - which points to MATCH DETACH DELETE not working correctly. What was happening is the following: some transaction would update the record in version list and set it's expiry to it's id. Along with that some transaction would query the mentioned record - and would set the hints flags for that expiration transaction status (which was aborted - which is fine at this moment). After some while, because the record is not really deleted because it's not aborted some other transaction would modify it's expiry transaction (this time making the transaction commited), but because the hints flags were not updated - they would still return the status for the old transaction - which was aborted. This made some records available even though they were deleted. Reviewers: mislav.bradac, florijan, teon.banek, matej.gradicek, buda Reviewed By: buda Subscribers: buda, lion, pullbot Differential Revision: https://phabricator.memgraph.io/D370 |
||
|---|---|---|
| .. | ||
| benchmark | ||
| concurrent | ||
| data | ||
| integration | ||
| manual | ||
| unit | ||
| client-stress.sh | ||
| CMakeLists.txt | ||