v3-0001-Add-doc-entry-for-the-new-GUC-paramenter-enable_g.patch
application/octet-stream
Filename: v3-0001-Add-doc-entry-for-the-new-GUC-paramenter-enable_g.patch
Type: application/octet-stream
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v3-0001
Subject: Add doc entry for the new GUC paramenter enable_group_by_reordering
| File | + | − |
|---|---|---|
| doc/src/sgml/config.sgml | 19 | 0 |
From 9a20dfd04a9dcd14beaf13773a6d1b695b67e36f Mon Sep 17 00:00:00 2001
From: Alexander Korotkov <akorotkov@postgresql.org>
Date: Tue, 18 Jun 2024 15:08:17 +0300
Subject: [PATCH v3] Add doc entry for the new GUC paramenter
enable_group_by_reordering
0452b461bc4 adds alternative orderings of group-by keys during the query
optimization. This new feature is controlled by the new GUC parameter
enable_group_by_reordering, which accidentally came without the documentation.
This commit adds the missing documentation for that GUC.
Reported-by: Bruce Momjian
Discussion: https://postgr.es/m/ZnDx2FYlba_OafQd%40momjian.us
Author: Andrei Lepikhov
---
doc/src/sgml/config.sgml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 698169afdb6..0c7a9082c54 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5341,6 +5341,25 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
</listitem>
</varlistentry>
+ <varlistentry id="guc-enable-groupby-reordering" xreflabel="enable_group_by_reordering">
+ <term><varname>enable_group_by_reordering</varname> (<type>boolean</type>)
+ <indexterm>
+ <primary><varname>enable_group_by_reordering</varname> configuration parameter</primary>
+ </indexterm>
+ </term>
+ <listitem>
+ <para>
+ Controls if the query planner will produce a plan which will provide
+ <literal>GROUP BY</literal> keys sorted 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 sorted 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 <literal>on</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry id="guc-enable-hashagg" xreflabel="enable_hashagg">
<term><varname>enable_hashagg</varname> (<type>boolean</type>)
<indexterm>
--
2.39.3 (Apple Git-145)