diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-07-19 11:00:34 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-07-19 11:00:34 -0400 |
commit | bc9993a5497748ca333beac34a8446114bfacce7 (patch) | |
tree | 39cbcd397b9cff18cf7cfe9089778c69d82c8056 /src | |
parent | f9278cb0ae947bd6b3ba88145ead6a991c5ddb5c (diff) | |
download | postgresql-bc9993a5497748ca333beac34a8446114bfacce7.tar.gz postgresql-bc9993a5497748ca333beac34a8446114bfacce7.zip |
Doc: improve description of IN and row-constructor comparisons.
IN and NOT IN work fine on records and arrays, so just say that
they accept "expressions" not "scalar expressions". I think that
that phrasing was meant to say that they don't work on set-returning
expressions, but that's not the common meaning of "scalar".
Revise the description of row-constructor comparisons to make it
perhaps a bit less confusing. (This partially reverts some
dubious wording changes made by commit f56651519.)
Per gripe from Ilya Nenashev. Back-patch to supported branches.
In HEAD and v16, also drop a NOTE about pre-8.2 behavior, which
is hopefully no longer of interest to anybody.
Discussion: https://postgr.es/m/168968062460.632.14303906825812821399@wrigleys.postgresql.org
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions