From: Tom Lane <tgl@sss.pgh.pa.us>
To: fed.guman@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Documentation mistake?
In-reply-to: <172979304162.700.15063986195610426211@wrigleys.postgresql.org>
References: <172979304162.700.15063986195610426211@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Thu, 24 Oct 2024 18:04:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2771917.1729867496.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 25 Oct 2024 10:44:56 -0400
Message-ID: <2771918.1729867496@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2771918.1729867496%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> In page https://www.postgresql.org/docs/current/indexes-bitmap-scans.html
> написано следующее:
> "Another example is that if we have separate indexes on x and y, one
> possible implementation of a query like WHERE x = 5 AND y = 6 is to use each
> index with the appropriate query clause and then AND together the index
> results to identify the result rows".

> You mean "WHERE x = 5 OR y = 6"?

No; the query says AND.  Unioning the index results would be
appropriate if it said OR, but that's a different topic.

			regards, tom lane