citus

Commit Graph

Author	SHA1	Message	Date
Halil Ozan Akgul	56e814a333	Adds public host to only hyperscale tests	2020-04-10 15:54:47 +03:00
Marco Slot	5b1d1dd413	Remove unnecessary use of max_parallel_workers_per_gather	2020-03-06 13:18:58 +01:00
Jelte Fennema	7730bd449c	Normalize tests: Remove trailing whitespace	2020-01-06 09:32:03 +01:00
Jelte Fennema	7f3de68b0d	Normalize tests: header separator length	2020-01-06 09:32:03 +01:00
Philip Dubé	c563e0825c	Strip trailing whitespace and add final newline (#3186 ) This brings files in line with our editorconfig file	2019-11-21 14:25:37 +01:00
Jason Petersen	d7f10b0896	Rewrite parallel ID test to avoid costly JITting By setting the CPU tuple cost so high, we were triggering JIT. Instead, we should use parallel_tuple_cost. See: rhaas.blogspot.com/2018/06/using-forceparallelmode-correctly.html	2018-09-24 09:29:53 +03:00
Marco Slot	9b520ae194	Add test for using transaction ID in parallel worker	2017-12-19 09:30:29 +01:00
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

8 Commits (dd5277418f8da96e17a501928e319d3a9962628a)