From: Tom Lane <tgl@sss.pgh.pa.us>
To: postgresql@wchargin.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: No search results for "BETWEEN"
In-reply-to: 
 <165600177616.879893.13980346362169630574@wrigleys.postgresql.org>
References: <165600177616.879893.13980346362169630574@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Thu, 23 Jun 2022 16:29:36 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <355732.1656081617.1@sss.pgh.pa.us>
Date: Fri, 24 Jun 2022 10:40:17 -0400
Message-ID: <355733.1656081617@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/355733.1656081617%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> Searching for "the between predicate simplifies range tests" does turn
> up a hit for that page, so it's indexed, but the words "The BETWEEN" are
> not set in bold in the search result. Perhaps "BETWEEN" is being treated
> as a stop word, even though it's capitalized and an SQL keyword?

A quick grep shows that if "between" weren't a stopword, it would
produce almost 600 hits in our core docs, most of which are not what
you're looking for.  So I concur with somebody's apparent decision
to make it a stopword.

Use the index.

			regards, tom lane