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
commit9ac7fa2776a9940692677f0e4f26fe7254803929 (patch)
tree478cbbaf3b59fcd6ef6e0dbfcf2eeff1e5b980e3
parentdb7394d4de7c0073a84f7d591a21bd6e00b2663c (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 3af337a65cb..711f7261724 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -129,6 +129,9 @@ TABLE [ ONLY ] <replaceable class="parameter">table_name</replaceable> [ * ]
eliminates groups that do not satisfy the given condition. (See
<xref linkend="sql-groupby"/> and
<xref linkend="sql-having"/> 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>