citus/src/backend/distributed/transaction
Jelte Fennema 2f29d4e53e Continue to remove shards after first failure in DropMarkedShards
The comment of DropMarkedShards described the behaviour that after a
failure we would continue trying to drop other shards. However the code
did not do this and would stop after the first failure. Instead of
simply fixing the comment I fixed the code, because the described
behaviour is more useful. Now a single shard that cannot be removed yet
does not block others from being removed.
2021-04-30 15:42:09 +03:00
..
backend_data.c Drop postgres 11 support 2021-03-25 09:20:28 +03:00
citus_dist_stat_activity.c Fix various typos due to zealous repetition 2021-03-04 19:28:15 +00:00
distributed_deadlock_detection.c use PG_USED_FOR_ASSERTS_ONLY 2020-03-25 11:01:33 +03:00
lock_graph.c Columnar: don't include stripe reservation locks in lock graph. 2021-02-10 10:20:20 -08:00
relation_access_tracking.c Fix various typos due to zealous repetition 2021-03-04 19:28:15 +00:00
remote_transaction.c Skip 2PC for readonly connections in a transaction (#4587) 2021-03-10 20:01:37 +03:00
transaction_management.c Remove unnecessary AtEOXact_Files call 2021-03-15 09:34:02 +01:00
transaction_recovery.c Drop postgres 11 support 2021-03-25 09:20:28 +03:00
worker_transaction.c Continue to remove shards after first failure in DropMarkedShards 2021-04-30 15:42:09 +03:00