From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: doc: use simpler language for NULL return from ANY/ALL
In-reply-to: <E1gIYyQ-00043H-Us@gemulon.postgresql.org>
References: <E1gIYyQ-00043H-Us@gemulon.postgresql.org>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Fri, 02 Nov 2018 12:54:50 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17405.1541168421.1@sss.pgh.pa.us>
Date: Fri, 02 Nov 2018 10:20:21 -0400
Message-ID: <17406.1541168421@sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> doc:  use simpler language for NULL return from ANY/ALL
> Previously the combination of "does not return" and "any row" caused
> ambiguity.

IMO this is not an improvement.  It's turned something that read
reasonably well into something that sounds like it was written by
a not very good speaker of English.  In particular, the lack of
grammatical matching between the two parts of the sentence is now
quite confusing:

    The result is NULL if no comparison with a subquery row returns true,
    and it returns NULL for at least one row.

The antecedent of "it" was clear before, and is not now, at least to me.

Maybe you could replace that clause with "..., and at least one comparison
returns NULL."

			regards, tom lane