Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1gBAWR-0003Sx-1Z
	for pgsql-docs@arkaria.postgresql.org; Sat, 13 Oct 2018 03:23:23 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1gBAWL-0001WJ-R9
	for pgsql-docs@arkaria.postgresql.org; Sat, 13 Oct 2018 03:23:17 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <bruce@momjian.us>)
	id 1gBAWL-0001WB-LV
	for pgsql-docs@lists.postgresql.org; Sat, 13 Oct 2018 03:23:17 +0000
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <bruce@momjian.us>)
	id 1gBAWH-0007Om-G9
	for pgsql-docs@lists.postgresql.org; Sat, 13 Oct 2018 03:23:16 +0000
Received: from bruce by momjian.us with local (Exim 4.84_2)
	(envelope-from <bruce@momjian.us>)
	id 1gBAWD-0005ph-VE; Fri, 12 Oct 2018 23:23:09 -0400
Date: Fri, 12 Oct 2018 23:23:09 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: KES <kes-kes@yandex.ru>, pgsql-docs@lists.postgresql.org
Subject: Re: Ambiguous usage of 'any' in explanation
Message-ID: <20181013032309.GA21857@momjian.us>
References: <153701242703.22334.1476830122267077397@wrigleys.postgresql.org>
 <20181011210934.GG7807@momjian.us>
 <CAKFQuwYo-oahQS_8x8ax06Gs_y_P02Hjokso3XCLvpOvZip-bQ@mail.gmail.com>
 <5831541539340923@iva8-3af116a85b74.qloud-c.yandex.net>
 <20181012150433.GA12966@momjian.us>
 <CAKFQuwYqEj_KaUdk83utOUJtEC6YnWio-kq1aN0=KE6ev4yhWA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKFQuwYqEj_KaUdk83utOUJtEC6YnWio-kq1aN0=KE6ev4yhWA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

On Fri, Oct 12, 2018 at 02:37:33PM -0700, David G. Johnston wrote:
> On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian <bruce@momjian.us> wrote:
> 
>     Sorry, but I don't like this wording.  The problem is that the
>     comparison has two row sets --- the left-hand side, and the right-hand
>     side.
> 
> 
> Huh...the left hand side must be a non-set scalar or row constructor.

I meant that each row feeds a value to the left-hand side to be
evaluated.

>       Each row on the left-hand side is compared with the row set on
>     the right.  I also don't like people thinking about the result of ANY
>     since it is really <comparison> ANY that is being used.
> 
> 
> Then there is some more rewording to be done since: "The result of ANY is
> “true” if any true result is obtained." (v10; 9.22.4)
> 
> Maybe:
> 
> The result of ANY is “true” if the comparison returns true for any subquery
> row; otherwise the result is “false” (or NULL if any of the comparisons result
> in unknown)

Sure.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +