diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-08-27 16:37:22 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-08-27 16:37:22 -0400 |
| commit | e352a005bc34d8d1a3b3529688996985001cfc62 (patch) | |
| tree | cb813118d5e8105d7ee4837cac15c3aabac82362 /src/backend/access/gist/gistscan.c | |
| parent | cf86803e8e8ede508b6900b833339f65d0eabd76 (diff) | |
| download | postgresql-e352a005bc34d8d1a3b3529688996985001cfc62.tar.gz postgresql-e352a005bc34d8d1a3b3529688996985001cfc62.zip | |
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
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions