Re: BUG #18208: ts_headline MinWords and MaxWords cannot be set to the same value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18208: ts_headline MinWords and MaxWords cannot be set to the same value
Date
Msg-id 1316294.1700493044@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18208: ts_headline MinWords and MaxWords cannot be set to the same value  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Filip Sedlák
Date:
Subject: B-tree Index corruption
Next
From: Tom Lane
Date:
Subject: Re: B-tree Index corruption