summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2023-09-26 17:31:06 -0400
committerBruce Momjian <bruce@momjian.us>2023-09-26 17:31:06 -0400
commit3d398ae4a5bb08ed146f94cedc4f4ca39dd8eed7 (patch)
treefc2668bee811271529f44de9a5d8c33ee04e67e0
parent26917ebea745b4254895b816e35375865cfa4177 (diff)
doc: mention GROUP BY columns can reference target col numbers
Reported-by: hape <postgres-hape@gmx.de> Discussion: https://postgr.es/m/168871536004.379168.9352636188330923805@wrigleys.postgresql.org Backpatch-through: 11
-rw-r--r--doc/src/sgml/ref/select.sgml3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 1eb8cc04281..474ee23bf25 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -130,6 +130,9 @@ TABLE [ ONLY ] <replaceable class="parameter">table_name</replaceable> [ * ]
eliminates groups that do not satisfy the given condition. (See
<xref linkend="sql-groupby" endterm="sql-groupby-title"/> and
<xref linkend="sql-having" endterm="sql-having-title"/> below.)
+ Although query output columns are nominally computed in the next
+ step, they can also be referenced (by name or ordinal number)
+ in the <literal>GROUP BY</literal> clause.
</para>
</listitem>