Re: SQL/JSON: JSON_TABLE - Mailing list pgsql-hackers

From Andres Freund
Subject Re: SQL/JSON: JSON_TABLE
Date
Msg-id 20220406165930.675nhhmudfehrfh6@alap3.anarazel.de
Whole thread Raw
In response to Re: SQL/JSON: JSON_TABLE  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: SQL/JSON: JSON_TABLE  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Hi,

On 2022-04-06 11:50:11 -0400, Andrew Dunstan wrote:
> It does work, but Tom prefers not to have the test at all, so I'll just
> rip it out.

If I understand correctly the reason a large table is needed is to test
parallelism, right? Wouldn't the better fix be to just tweak the parallelism
settings for that table? See select_parallel.sql:

-- encourage use of parallel plans
set parallel_setup_cost=0;
set parallel_tuple_cost=0;
set min_parallel_table_scan_size=0;
set max_parallel_workers_per_gather=4;

might be worth also setting
set parallel_leader_participation = off;

to avoid the leader processing everything before workers have even started up.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] pg_stat_toast
Next
From: Andres Freund
Date:
Subject: Re: psql - add SHOW_ALL_RESULTS option - pg_regress output