Re: Question of Parallel Hash Join on TPC-H Benchmark
От | Andrei Lepikhov |
---|---|
Тема | Re: Question of Parallel Hash Join on TPC-H Benchmark |
Дата | |
Msg-id | 978176f8-14a5-4f4d-8925-07d2e7dec4ce@gmail.com обсуждение исходный текст |
Ответ на | Re: Question of Parallel Hash Join on TPC-H Benchmark (Ba Jinsheng <bajinsheng@u.nus.edu>) |
Ответы |
Re: Question of Parallel Hash Join on TPC-H Benchmark
|
Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: