From: Tom Lane <tgl@sss.pgh.pa.us>
To: oliverfwales@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18208: ts_headline MinWords and MaxWords cannot be set to
 the same value
In-reply-to: <18208-c695b6b402c37727@postgresql.org>
References: <18208-c695b6b402c37727@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 20 Nov 2023 14:04:26 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1316293.1700493044.1@sss.pgh.pa.us>
Date: Mon, 20 Nov 2023 10:10:44 -0500
Message-ID: <1316294.1700493044@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1316294.1700493044%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Setting MaxWords and MinWords to the same value (e.g. 30) in the options of
> ts_headline throws the error "MinWords should be less than MaxWords". Is
> there any reason why they must be different? Why not allow setting them to
> the same value to allow a fixed number of words to be returned?

[ shrug... ] I'd turn that around: why would that be a good idea?
Usually, you want quite a bit of room between MinWords and MaxWords
to allow a more-or-less-apropos text snippet to be returned.
It seems highly unlikely that the calling query knows enough about
the right snippet length (in advance of knowing the match) to get
good results by demanding an exact length.

			regards, tom lane