From: Tom Lane <tgl@sss.pgh.pa.us>
To: Corey Csuhta <its+postgres@csuhta.com>
cc: pgsql-bugs@postgresql.org
Subject: Re: Re: BUG #14623: pg_trgm doesn't correctly process some regexp
 with negative lookahead
In-reply-to: <E2B01A4B-4530-406B-8D17-2F67CF9A16BA@csuhta.com>
References: <E2B01A4B-4530-406B-8D17-2F67CF9A16BA@csuhta.com>
Comments: In-reply-to Corey Csuhta <its+postgres@csuhta.com>
	message dated "Thu, 13 Apr 2017 16:04:08 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <22557.1492145650.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Apr 2017 00:54:10 -0400
Message-ID: <22558.1492145650@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

Corey Csuhta <its+postgres@csuhta.com> writes:
> I don=E2=80=99t know if this is related or a separate bug, but I am also =
having this problem with the `+` operator and character classes. Very simil=
ar test case:
> CREATE TABLE foobar (x text);
> INSERT INTO foobar VALUES ('Trying +1/+1'),('Also doing +20/+20');
> CREATE EXTENSION pg_trgm;
> CREATE INDEX ON foobar USING gin (x gin_trgm_ops);
> SET enable_seqscan TO on;
> SELECT * FROM foobar WHERE x  ~ '\+\d+\/\+\d+'; -- Returns both rows
> SET enable_seqscan TO off;
> SELECT * FROM foobar WHERE x  ~ '\+\d+\/\+\d+'; -- Returns 0 rows

Hmm ... seems unrelated, since there's no lookahead constraint in this
example.  Also, the patch I committed earlier today doesn't fix it.

			regards, tom lane


--=20
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs