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 1gBGBG-0002ms-Tt
	for pgsql-docs@arkaria.postgresql.org; Sat, 13 Oct 2018 09:25:57 +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 1gBGBE-0005hL-FL
	for pgsql-docs@arkaria.postgresql.org; Sat, 13 Oct 2018 09:25:52 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <kes-kes@yandex.ru>)
	id 1gBGBE-0005hD-3a
	for pgsql-docs@lists.postgresql.org; Sat, 13 Oct 2018 09:25:52 +0000
Received: from forward105j.mail.yandex.net ([5.45.198.248])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <kes-kes@yandex.ru>)
	id 1gBGB5-00040j-Ba
	for pgsql-docs@lists.postgresql.org; Sat, 13 Oct 2018 09:25:50 +0000
Received: from mxback9g.mail.yandex.net (mxback9g.mail.yandex.net
 [IPv6:2a02:6b8:0:1472:2741:0:8b7:170])
	by forward105j.mail.yandex.net (Yandex) with ESMTP id 6551A184AF2;
	Sat, 13 Oct 2018 12:25:39 +0300 (MSK)
Received: from localhost (localhost [::1])
	by mxback9g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id
 EwWVjeJf6O-Pcb8YuVD;
	Sat, 13 Oct 2018 12:25:38 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
 t=1539422738;
	bh=SdaXsROQ2vl1EezBZimap2sodyueFBleMzSYhb3rLXY=;
	h=From:To:Cc:In-Reply-To:References:Subject:Date:Message-Id;
	b=qcKMX4LMJ+0kQBdDXhgzCglfILXQXe7zhI40hwzS9KP/PVVlu3IaeKs0Av58AdIP1
	 G126Bhq+AVCz4zHMenjRycb3az73areGyzCrYMobOxhW98bnTRfC38dUU5iFLICCLS
	 EduPg4ZgiVSZtPXiQUBPJ+/0B2l2RzwmCUgqd1QY=
Authentication-Results: mxback9g.mail.yandex.net;
 dkim=pass header.i=@yandex.ru
Received: by sas1-00d5718ef836.qloud-c.yandex.net with HTTP;
	Sat, 13 Oct 2018 12:25:38 +0300
From: KES <kes-kes@yandex.ru>
Envelope-From: kes-kes@yandex.com
To: David G. Johnston <david.g.johnston@gmail.com>,
	Bruce Momjian <bruce@momjian.us>
Cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
In-Reply-To: 
 <CAKFQuwYqEj_KaUdk83utOUJtEC6YnWio-kq1aN0=KE6ev4yhWA@mail.gmail.com>
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>
Subject: Re: Ambiguous usage of 'any' in explanation
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Sat, 13 Oct 2018 12:25:38 +0300
Message-Id: <1806231539422738@sas1-00d5718ef836.qloud-c.yandex.net>
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8
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

<div xmlns="http://www.w3.org/1999/xhtml"><font face="arial, helvetica, sans-serif">&gt;or NULL if any of the comparisons result in unknown</font></div><div xmlns="http://www.w3.org/1999/xhtml">result in unknown??</div><div xmlns="http://www.w3.org/1999/xhtml"> </div><div><br /></div><div><br /></div><div>13.10.2018, 00:37, "David G. Johnston" &lt;david.g.johnston@gmail.com&gt;:</div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif;"><span style="font-family:Arial,Helvetica,sans-serif;">On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian &lt;<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>&gt; wrote:</span><br /></div><div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">Sorry, but I don't like this wording.  The problem is that the<br />
comparison has two row sets --- the left-hand side, and the right-hand<br />
side.</blockquote><div><br /></div><div style="font-family:arial,helvetica,sans-serif;">Huh...the left hand side must be a non-set scalar or row constructor.</div><div><br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">  Each row on the left-hand side is compared with the row set on<br />
the right.  I also don't like people thinking about the result of ANY<br />
since it is really &lt;comparison&gt; ANY that is being used.<br /></blockquote><div><br /></div><div style="font-family:arial,helvetica,sans-serif;">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)</div><div style="font-family:arial,helvetica,sans-serif;"><br /></div><div style="font-family:arial,helvetica,sans-serif;">Maybe:</div><div style="font-family:arial,helvetica,sans-serif;"><br /></div><div><font face="arial, helvetica, sans-serif">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)</font><br /></div><div><font face="arial, helvetica, sans-serif"><br /></font></div><div><font face="arial, helvetica, sans-serif">David J.</font></div><div><font face="arial, helvetica, sans-serif"><br /></font></div></div></div></div></div>
</blockquote>