On 10/10/2024 23:52, Ba Jinsheng wrote:
> Thanks for your replies!
>
>
> I configured these variables and did get a worse query plan:
Could you provide SQL dump and settings to play with this case locally?
I would discover what we need to transform Subplan 1 into a SEMI JOIN.
Also, I usually force parallel workers with settings like below:
max_parallel_workers_per_gather = 32
min_parallel_table_scan_size = 0
min_parallel_index_scan_size = 0
max_worker_processes = 64
parallel_setup_cost = 0.001
parallel_tuple_cost = 0.0001
just to be sure, it's not the case when something down the plan tree
forbids generating a parallel query plan.
P.S.
To discover other options, the AQO extension may be helpful. It stores
cardinalities from all plan nodes after execution and uses them to
calculate selectivities on the subsequent execution.
--
regards, Andrei Lepikhov
