| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Ba Jinsheng <bajinsheng(at)u(dot)nus(dot)edu> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Zhang Mingli <zmlpostgres(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Question of Parallel Hash Join on TPC-H Benchmark |
| Date: | 2024-10-13 00:01:29 |
| Message-ID: | c293883e-dcc5-4a21-9293-ed10105f5f46@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 13/10/2024 01:11, Ba Jinsheng wrote:
> I changed the code to generate an efficient query plan (only the
> HashJoin in fifth line is in parallel), so I am wondering whether it is
> possible to optimize the code to enable this efficient query plan in
> default? I believe at least, it would improve the performance of
> PostgreSQL on the standard benchmark TPC-H.
> If you need, I can provide my environment in docker for your analysis.
Thanks for sharing the case! I will investigate it in a while.
--
regards, Andrei Lepikhov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-10-13 03:09:29 | Re: Question of Parallel Hash Join on TPC-H Benchmark |
| Previous Message | Tom Lane | 2024-10-12 19:13:47 | Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index |