database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Forgot to back-patch earlier change to documentation for aggregate

Browse Source 
ORDER BY clauses.
This commit is contained in:
Tom Lane
2010-08-04 22:31:55 +00:00
parent 5e84e1ac05
commit 6a366113e6
1 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/sgml/syntax.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.147 2010/07/03 02:57:46 rhaas Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/syntax.sgml,v 1.147.2.1 2010/08/04 22:31:55 tgl Exp $ -->
<chapter id="sql-syntax"> <chapter id="sql-syntax">
<title>SQL Syntax</title> <title>SQL Syntax</title>
@ -1568,7 +1568,7 @@ sqrt(2)
unspecified order. In many cases this does not matter; for example, unspecified order. In many cases this does not matter; for example,
<function>min</> produces the same result no matter what order it <function>min</> produces the same result no matter what order it
receives the inputs in. However, some aggregate functions receives the inputs in. However, some aggregate functions
(such as <function>array_agg</> and <function>xmlagg</>) produce (such as <function>array_agg</> and <function>string_agg</>) produce
results that depend on the ordering of the input rows. When using results that depend on the ordering of the input rows. When using
such an aggregate, the optional <replaceable>order_by_clause</> can be such an aggregate, the optional <replaceable>order_by_clause</> can be
used to specify the desired ordering. The <replaceable>order_by_clause</> used to specify the desired ordering. The <replaceable>order_by_clause</>
@ -1576,12 +1576,26 @@ sqrt(2)
described in <xref linkend="queries-order">, except that its expressions described in <xref linkend="queries-order">, except that its expressions
are always just expressions and cannot be output-column names or numbers. are always just expressions and cannot be output-column names or numbers.
For example: For example:
<programlisting> <programlisting>
SELECT array_agg(a ORDER BY b DESC) FROM table; SELECT array_agg(a ORDER BY b DESC) FROM table;
</programlisting> </programlisting>
</para> </para>
<para>
When dealing with multiple-argument aggregate functions, note that the
<literal>ORDER BY</> clause goes after all the aggregate arguments.
For example, this:
<programlisting>
SELECT string_agg(a, ',' ORDER BY a) FROM table;
</programlisting>
not this:
<programlisting>
SELECT string_agg(a ORDER BY a, ',') FROM table; -- not what you want
</programlisting>
The latter syntax will be accepted, but <literal>','</> will be
treated as a (useless) sort key.
</para>
<para> <para>
If <literal>DISTINCT</> is specified in addition to an If <literal>DISTINCT</> is specified in addition to an
<replaceable>order_by_clause</>, then all the <literal>ORDER BY</> <replaceable>order_by_clause</>, then all the <literal>ORDER BY</>