On Wed, Feb 10, 2016 at 4:28 AM, Oleg Bartunov wrote:
> It looks like there is a very old bug in full text parser (somebody pointed
> me on it), which appeared after moving tsearch2 into the core. The problem
> is in how full text parser process hyphenated words. Our
Oleg Bartunov writes:
> It looks like there is a very old bug in full text parser (somebody
> pointed me on it), which appeared after moving tsearch2 into the core. The
> problem is in how full text parser process hyphenated words. Our original
> idea was to report
On Wed, Feb 10, 2016 at 7:21 PM, Tom Lane wrote:
> Oleg Bartunov writes:
> > It looks like there is a very old bug in full text parser (somebody
> > pointed me on it), which appeared after moving tsearch2 into the core.
> The
> > problem is in how full
On Wed, Feb 10, 2016 at 7:45 PM, Mike Rylander wrote:
> On Wed, Feb 10, 2016 at 4:28 AM, Oleg Bartunov
> wrote:
> > It looks like there is a very old bug in full text parser (somebody
> pointed
> > me on it), which appeared after moving tsearch2 into
On Wed, Feb 10, 2016 at 12:28 PM, Oleg Bartunov wrote:
> It looks like there is a very old bug in full text parser (somebody
> pointed me on it), which appeared after moving tsearch2 into the core. The
> problem is in how full text parser process hyphenated words. Our
It looks like there is a very old bug in full text parser (somebody
pointed me on it), which appeared after moving tsearch2 into the core. The
problem is in how full text parser process hyphenated words. Our original
idea was to report hyphenated word itself as well as its parts and ignore