Skip to content

Commit 24987c6

Browse files
committed
doc PG 18 relnotes: add GROUP BY column elimination item
With a nod to PG 9.6. Reported-by: jian he Discussion: https://postgr.es/m/CACJufxEqs=EXZETwtaOooTFhZrtxvSWg8M2uPfzjNtS3wQ6Dzw@mail.gmail.com
1 parent 04b269d commit 24987c6

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

doc/src/sgml/release-18.sgml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -284,6 +284,23 @@ This optimization can be disabled using enable_distinct_reordering.
284284
</para>
285285
</listitem>
286286

287+
<!--
288+
Author: David Rowley <drowley@postgresql.org>
289+
2024-12-12 [bd10ec529] Detect redundant GROUP BY columns using UNIQUE indexes
290+
-->
291+
292+
<listitem>
293+
<para>
294+
Ignore GROUP BY columns that are functionally dependent on other columns (Zhang Mingli, Jian He, David Rowley)
295+
<ulink url="&commit_baseurl;bd10ec529">&sect;</ulink>
296+
</para>
297+
298+
<para>
299+
If a GROUP BY clause includes all columns of a unique index, as well as other columns of the same table, those other columns are redundant and can be dropped
300+
from the grouping. This was already true for non-deferred primary keys.
301+
</para>
302+
</listitem>
303+
287304
<!--
288305
Author: Richard Guo <rguo@postgresql.org>
289306
2024-10-09 [67a54b9e8] Allow pushdown of HAVING clauses with grouping sets

0 commit comments

Comments
 (0)