mirror of https://github.com/citusdata/citus.git
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.htmlpull/2356/head
parent
e62a1ab43d
commit
d7f10b0896
|
@ -143,8 +143,8 @@ CREATE UNLOGGED TABLE parallel_id_test AS
|
|||
SELECT s AS a, s AS b, s AS c, s AS d, s AS e, s AS f, s AS g, s AS h FROM generate_series(1,150000) s;
|
||||
INSERT INTO parallel_id_test VALUES (1234567), (1234567), (1234568), (1234568);
|
||||
ANALYSE parallel_id_test;
|
||||
SET LOCAL max_parallel_workers_per_gather TO 8;
|
||||
SET LOCAL cpu_tuple_cost TO 1000000;
|
||||
SET LOCAL max_parallel_workers_per_gather TO 2;
|
||||
SET LOCAL parallel_tuple_cost TO 0;
|
||||
EXPLAIN (COSTS OFF)
|
||||
SELECT a FROM parallel_id_test WHERE a = parallel_worker_transaction_id_test();
|
||||
QUERY PLAN
|
||||
|
|
|
@ -96,8 +96,8 @@ SELECT s AS a, s AS b, s AS c, s AS d, s AS e, s AS f, s AS g, s AS h FROM gener
|
|||
INSERT INTO parallel_id_test VALUES (1234567), (1234567), (1234568), (1234568);
|
||||
ANALYSE parallel_id_test;
|
||||
|
||||
SET LOCAL max_parallel_workers_per_gather TO 8;
|
||||
SET LOCAL cpu_tuple_cost TO 1000000;
|
||||
SET LOCAL max_parallel_workers_per_gather TO 2;
|
||||
SET LOCAL parallel_tuple_cost TO 0;
|
||||
|
||||
EXPLAIN (COSTS OFF)
|
||||
SELECT a FROM parallel_id_test WHERE a = parallel_worker_transaction_id_test();
|
||||
|
|
Loading…
Reference in New Issue