diff options
author | Bruce Momjian | 2023-09-26 21:31:06 +0000 |
---|---|---|
committer | Bruce Momjian | 2023-09-26 21:31:32 +0000 |
commit | 1b5a00450acb34d4aa4565aa54fe79c6676f8236 (patch) | |
tree | eda1ce235f4ddae3dcb8540996a66f8574ca9c5b | |
parent | 639e1aa81f3d0dddd9ff9b54abb7edabd2277af1 (diff) |
doc: mention GROUP BY columns can reference target col numbers
Reported-by: hape <[email protected]>
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 11
-rw-r--r-- | doc/src/sgml/ref/select.sgml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 0ee0cc7e641..42d78913cf9 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -131,6 +131,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> |