Re: Add enable_groupagg GUC parameter to control GroupAggregate usage

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tatsuro Yamada <tatsuro(dot)yamada(at)ntt(dot)com>
Cc: Tatsuro Yamada <yamatattsu(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add enable_groupagg GUC parameter to control GroupAggregate usage
Date: 2026-07-07 06:53:20
Message-ID: CAMbWs4-0UTTMNftuJBpZuUp1zzGWjFgkHSnwaqZdKG2Lo1fJAA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 7, 2026 at 3:47 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Attached is a rebased patch to make cfbot work again.

I intend to push this patch soon. That way newly added test cases can
start using enable_groupagg directly. Otherwise we'll have to keep
rebasing it to convert any new tests that use enable_sort to force
hashed grouping. Any thoughts?

- Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-07-07 06:54:50 Re: [PATCH] GROUP BY ALL
Previous Message Richard Guo 2026-07-07 06:47:21 Re: Add enable_groupagg GUC parameter to control GroupAggregate usage