Re: Missing docs for new enable_group_by_reordering GUC

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
Cc: Andrei Lepikhov <lepihov(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Missing docs for new enable_group_by_reordering GUC
Date: 2024-06-19 01:27:31
Message-ID: CAPpHfdtTggaWkyh3d_4-WHruXSBA1=5S1VhpGExtLC0jfTmeEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 18, 2024 at 4:14 PM Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> wrote:
>> Controls if the query planner will produce a plan which will provide <literal>GROUP BY</literal> keys presorted in the order of keys of a child node of the plan, such as an index scan. When disabled, the query planner will produce a plan with <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.

------
Regards,
Alexander Korotkov
Supabase

Attachment Content-Type Size
v3-0001-Add-doc-entry-for-the-new-GUC-paramenter-enable_g.patch application/octet-stream 2.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2024-06-19 01:42:32 Re: Better error message when --single is not the first arg to postgres executable
Previous Message Peter Geoghegan 2024-06-19 01:16:43 Re: Revive num_dead_tuples column of pg_stat_progress_vacuum