| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tender Wang <tndrwang(at)gmail(dot)com>, Paul George <p(dot)a(dot)george19(at)gmail(dot)com>, Andy Fan <zhihuifan1213(at)163(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Eager aggregation, take 3 |
| Date: | 2025-10-02 01:13:48 |
| Message-ID: | CAMbWs4_v2P2hWbENT8UZG-t_A9TuPGJYas29FUcqx9EoETG6Gg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 2, 2025 at 8:55 AM Matheus Alcantara
<matheusssilv97(at)gmail(dot)com> wrote:
> The query 31 seems bad, I don't know if I'm doing something completely
> wrong but I've just setup a TPC-DS database and then executed the query
> on master and with the v23 patch and I got these results:
>
> Master:
> Planning Time: 3.191 ms
> Execution Time: 16950.619 ms
>
> Patch:
> Planning Time: 3.257 ms
> Execution Time: 3848355.646 ms
Thanks for reporting this. It does seem odd. I checked the TPC-DS
benchmarking on v13 and found that the execution time for query 31,
with and without eager aggregation, is as follows:
EAGER-AGG-OFF EAGER-AGG-ON
q31 10463.536 ms 10244.175 ms
There appears to be a regression between v13 and v23. Looking into
it...
- Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-10-02 01:23:11 | Re: relfilenode statistics |
| Previous Message | Matheus Alcantara | 2025-10-01 23:54:32 | Re: Eager aggregation, take 3 |