Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cylHd-0007nC-89 for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Apr 2017 20:24:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cylHc-00055Z-Ct for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Apr 2017 20:24:00 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cykyS-0000YO-BZ for pgsql-bugs@postgresql.org; Thu, 13 Apr 2017 20:04:12 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cykyP-0007CB-NP for pgsql-bugs@postgresql.org; Thu, 13 Apr 2017 20:04:11 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3DE7C209FE for ; Thu, 13 Apr 2017 16:04:09 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 13 Apr 2017 16:04:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=csuhta.com; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=8M02lC31il2SXRip5o8peAJYP/9Yii4duytKRA 4f/gM=; b=jjqOroMO3FVRKgeAlZtrALTFH7oKN7xYI0p7qiX20LKatpKhHjm9lM YIjkrjwJLJeethcgtoXIf+tdolTKvQ0vbftpVvgFQscNMEAlaD43NovkFvsKdOmj zu40wsOGh70WXtIyLNgz6c/QLJiA5eTNvieeO90Ewb44q9aQfZO8I= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=8M02lC31il2SXRip5o 8peAJYP/9Yii4duytKRA4f/gM=; b=b3QVvN/kJsXoSZ5K8BkBGj8VO1uKg4iwdT lb8JDYTD6fTHcZpzKn//zNs3skGO38MExe1FOmyhQ07r46xq8N948YLX70NpM3qR gSC/lAw+nWs/x8n8dgbbDwBtcMVVQpXcbI2eANU9HbNvyFfNGsaW++ymAqbnCKUG Ep+PM5Bd8kZBLqZ3kBsUa+3NXs400aHGqpo66es3CE74lTYdP4q3MYoa0RZ4NKF0 LWterUtFNJcsRwv1jKaHqpsjVKbhq5Jpte9aJbBdekq7HkOdv+C58/lSGlbByIJj XZVQuhlaeE+uRO90CpiDzkqzdeAqCtL9adlzApfcTB4aw7OW8GXw== X-ME-Sender: X-Sasl-enc: RU95Q9zGdtLrHThlTFpZ1/YQoMCgLjT3N8v4+5a3e3Bj 1492113849 Received: from thanatos.csuhta.com (c-73-133-10-210.hsd1.va.comcast.net [73.133.10.210]) by mail.messagingengine.com (Postfix) with ESMTPA id 0F20A248C9 for ; Thu, 13 Apr 2017 16:04:09 -0400 (EDT) From: Corey Csuhta Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: BUG #14623: pg_trgm doesn't correctly process some regexp with negative lookahead Message-Id: Date: Thu, 13 Apr 2017 16:04:08 -0400 To: pgsql-bugs@postgresql.org X-Mailer: Apple Mail (2.3273) X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org I don=E2=80=99t know if this is related or a separate bug, but I am also ha= ving this problem with the `+` operator and character classes. Very similar= 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 --=20 Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs