Re: Eager aggregation, take 3

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: 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: 2024-10-30 13:09:37
Message-ID: CA+TgmoZAmuHqja8Y8g7beekTgt2TsmW+tnw9+c7GOikPR+KGYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 5, 2024 at 11:30 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Here’s a comparison of Execution Time and Planning Time for the seven
> queries with eager aggregation disabled versus enabled (best of 3).
>
> Execution Time:
>
> EAGER-AGG-OFF EAGER-AGG-ON
>
> q4 105787.963 ms 34807.938 ms
> q8 1407.454 ms 1654.923 ms
> q11 67899.213 ms 18670.086 ms
> q23 45945.849 ms 42990.652 ms
> q31 10463.536 ms 10244.175 ms
> q33 2186.928 ms 2217.228 ms
> q77 2360.565 ms 2416.674 ms

Could you attach the EXPLAIN ANALYZE output for these queries, with
and without the patch?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikita Malakhov 2024-10-30 13:23:01 Re: detoast datum into the given buffer as a optimization.
Previous Message Ashutosh Bapat 2024-10-30 12:46:12 Re: Alias of VALUES RTE in explain plan