Jelte Fennema 02fa942be1 Fix assertion error when rolling back to savepoint (#3868) ... It was possible to get an assertion error, if a DML command was cancelled that opened a connection and then "ROLLBACK TO SAVEPOINT" was used to continue the transaction. The reason for this was that canceling the transaction might leave the `claimedExclusively` flag on for (some of) it's connections. This caused an assertion failure because `CanUseExistingConnection` would return false and a new connection would be opened, and then there would be two connections doing DML for the same placement. Which is disallowed. That this situation caused an assertion failure instead of an error, means that without asserts this could possibly result in some visibility bugs, similar to the ones described https://github.com/citusdata/citus/issues/3867		2020-06-30 11:31:46 +02:00
..
hammerdb	rename citus hammerdb branch prefix as citus_github_push (#3925)	2020-06-18 21:11:58 +03:00
regress	Fix assertion error when rolling back to savepoint (#3868)	2020-06-30 11:31:46 +02:00
scripts	Make check_enterprise_merge script stricter (#3918)	2020-06-19 12:45:36 +02:00