From: Tom Lane <tgl@sss.pgh.pa.us>
To: eric.mutta@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Bug in code sample in "8.15.5. Searching in Arrays"
In-reply-to: <165852967722.271454.6988634580136979082@wrigleys.postgresql.org>
References: <165852967722.271454.6988634580136979082@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Fri, 22 Jul 2022 22:41:17 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1738246.1658691671.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 24 Jul 2022 15:41:11 -0400
Message-ID: <1738247.1658691671@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1738247.1658691671%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> The section on array searching here:
>       https://www.postgresql.org/docs/current/arrays.html#ARRAYS-SEARCHI=
NG
> ...says "In addition, you can find rows where the array has all values e=
qual
> to 10000 with:"  and gives the following code example:
>       SELECT * FROM sal_emp WHERE 10000 =3D ALL (pay_by_quarter);

Yeah ...

> ...however the docs for "ALL" over here:
> https://www.postgresql.org/docs/current/functions-comparisons.html#id-1.=
5.8.30.17
> ...explicitly say that "The result of ALL is =E2=80=9Ctrue=E2=80=9D if a=
ll comparisons yield
> true (including the case where the array has zero elements)."

I don't see any conflict there.

			regards, tom lane