5 Commits (3369f3486f8dd33b7cd45eef47f48b1e6e304da2)

Author	SHA1	Message	Date
Onder Kalaci	3369f3486f	Introduce distributed transaction ids ... This commit adds distributed transaction id infrastructure in the scope of distributed deadlock detection. In general, the distributed transaction id consists of a tuple in the form of: `(databaseId, initiatorNodeIdentifier, transactionId, timestamp)`. Briefly, we add a shared memory block on each node, which holds some information per backend (i.e., an array `BackendData backends[MaxBackends]`). Later, on each coordinated transaction, Citus sends `SELECT assign_distributed_transaction_id()` right after `BEGIN`. For that backend on the worker, the distributed transaction id is set to the values assigned via the function call. The aim of the above is to correlate the transactions on the coordinator to the transactions on the worker nodes.	2017-07-18 15:01:42 +03:00
Andres Freund	3461244539	Don't wait for statement completion when aborting coordinated transaction. ... Previously we used ForgetResults() in StartRemoteTransactionAbort() - that's problematic because there might still be an ongoing statement, and this causes us to wait for its completion. That e.g. happens when a statement running on the coordinator is cancelled.	2017-07-04 14:46:03 -07:00
Andres Freund	ec0ed677e3	Fix copy & pasto in WARNING message.	2017-07-04 12:38:52 -07:00
Marco Slot	6cbc1945f9	Enable transaction recovery in connection API	2016-12-23 16:14:29 +01:00
Andres Freund	fc298ec095	Coordinated remote transaction management.	2016-12-12 15:18:12 -08:00