Re: Add enable_presorted_aggregate GUC

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add enable_presorted_aggregate GUC
Date: 2022-12-20 09:31:54
Message-ID: CAApHDvp2-2TfCxsqbSy1-ft=Xi-+_uUN1tFJG=KYZAJo2UCw4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 16 Dec 2022 at 12:47, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> Normally we add some enable_* GUC to leave an escape hatch when we add
> some new feature like this. I likely should have done that when I
> added 1349d279, but I didn't and I want to now.
>
> I mainly just shifted this discussion out of [1] as we normally like
> to debate GUC names and I feel that the discussion over on the other
> thread is buried a little too deep to be visible to most people.
>
> Can anyone think of a better name? Or does anyone see error with my ambition?

I've now pushed this.

I'm still happy to consider other names if anyone has any good ideas,
but so far it's all quiet here, so I've assumed that's a good thing.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2022-12-20 09:51:59 Re: Minimal logical decoding on standbys
Previous Message Vik Fearing 2022-12-20 09:24:22 Container Types