Re: Missing docs for new enable_group_by_reordering GUC - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Missing docs for new enable_group_by_reordering GUC
Date
Msg-id CAPpHfdugtpt3u_cA9wJKqiGURyN+mSXhnJ2QZc6fESTCwwtqNw@mail.gmail.com
Whole thread Raw
In response to Re: Missing docs for new enable_group_by_reordering GUC  (Pavel Borisov <pashkin.elfe@gmail.com>)
List pgsql-hackers
On Wed, Jun 19, 2024 at 6:02 PM Pavel Borisov <pashkin.elfe@gmail.com> wrote:
> On Wed, 19 Jun 2024 at 05:27, Alexander Korotkov <aekorotkov@gmail.com> wrote:
>>
>> On Tue, Jun 18, 2024 at 4:14 PM Pavel Borisov <pashkin.elfe@gmail.com> wrote:
>> >> Controls if the query planner will produce a plan which will provide <literal>GROUP BY</literal> keys presorted
inthe order of keys of a child node of the plan, such as an index scan. When disabled, the query planner will produce a
planwith <literal>GROUP BY</literal> keys only reordered to match 
>> >> the <literal>ORDER BY</literal> clause, if any. When enabled, the planner will try to produce a more efficient
plan.The default value is on. 
>> > A correction of myself: presorted -> sorted, reordered ->sorted
>>
>> Thank you for your review.  I think all of this make sense.  Please,
>> check the revised patch attached.
>
> To me patch v3 looks good.

Ok, thank you. I'm going to push this if no objections.

------
Regards,
Alexander Korotkov
Supabase



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: remove check hooks for GUCs that contribute to MaxBackends
Next
From: Alexander Lakhin
Date:
Subject: Re: Failures in constraints regression test, "read only 0 of 8192 bytes"