pgsql: Doc: clarify behavior of standard aggregates for null inputs.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: clarify behavior of standard aggregates for null inputs.
Date: 2019-08-27 20:37:46
Message-ID: E1i2iDq-0005sS-03@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: clarify behavior of standard aggregates for null inputs.

Section 4.2.7 says that unless otherwise specified, built-in
aggregates ignore rows in which any input is null. This is
not true of the JSON aggregates, but it wasn't documented.
Fix that.

Of the other entries in table 9.55, some were explicit about
ignoring nulls, and some weren't; for consistency and
self-contained-ness, make them all say it explicitly.

Per bug #15884 from Tim Möhlmann. Back-patch to all supported
branches.

Discussion: https://postgr.es/m/15884-c32d848f787fcae3@postgresql.org

Branch
------
REL9_6_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/5efa4a3e7008638732d14ffd7613f53823a75367

Modified Files
--------------
doc/src/sgml/func.sgml | 26 +++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2019-08-27 21:02:48 pgsql: Remove obsolete nbtree page deletion comment.
Previous Message Tom Lane 2019-08-27 20:37:45 pgsql: Doc: clarify behavior of standard aggregates for null inputs.