Re: BUG #14245: Segfault on weird to_tsquery - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14245: Segfault on weird to_tsquery
Date
Msg-id 6712.1468357892@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14245: Segfault on weird to_tsquery  (David Kellum <david@gravitext.com>)
Responses Re: BUG #14245: Segfault on weird to_tsquery
List pgsql-bugs
David Kellum <david@gravitext.com> writes:
> On Tue, Jul 12, 2016 at 12:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Note that while crashing is certainly not good, the pre-9.6 behavior
>> can hardly be called correct either.  What happened to 'a'?

> 'a' is a stopword, dropped by to_tsquery() as described here:

Ah!  OK, so it's probably necessary to have a stopword there in order
to break it.

BTW, all these variants also crash:

select to_tsquery('!(a | !b) & c') as tsquery;
select to_tsquery('!( !b & a) & c') as tsquery;
select to_tsquery('!( !b | a) & c') as tsquery;

            regards, tom lane

pgsql-bugs by date:

Previous
From: David Kellum
Date:
Subject: Re: BUG #14245: Segfault on weird to_tsquery
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file