On Tue, Aug 9, 2016 at 01:58:25PM -0400, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Does anyone know why the phrase distance "<3>" was changed from "at most > > three tokens away" to "exactly three tokens away"? > > So that it would correctly support phraseto_tsquery's use of the operator > to represent omitted words (stopwords) in a phrase. > > I think there's probably some use in also providing an operator that does > "at most this many tokens away", but Oleg/Teodor were evidently less > excited, because they didn't take the time to do it. > > The thread where this change was discussed is > > https://www.postgresql.org/message-id/flat/c19fcfec308e6ccd952cdde9e648b505%40mail.gmail.com > > see particularly > > https://www.postgresql.org/message-id/11252.1465422251%40sss.pgh.pa.us
Ah, I know it was discussed somewhere. Thanks, the phraseto_tsquery tie-in was what I forgot. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
