Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cgYfk-0004cW-4v for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2017 15:17:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cgYfj-0005li-Kv for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2017 15:17:39 +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 1cgYf4-0004iC-FS for pgsql-bugs@postgresql.org; Wed, 22 Feb 2017 15:16:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cgYf2-0007zV-8u for pgsql-bugs@postgresql.org; Wed, 22 Feb 2017 15:16:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v1MFGsNP032282; Wed, 22 Feb 2017 10:16:54 -0500 From: Tom Lane To: isayko.alexey@gmail.com cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14563: count(*) gives a wrong result in PostgreSQL for some regex with pg_trm/GIN index In-reply-to: <20170222111446.1256.67547@wrigleys.postgresql.org> References: <20170222111446.1256.67547@wrigleys.postgresql.org> Comments: In-reply-to isayko.alexey@gmail.com message dated "Wed, 22 Feb 2017 11:14:46 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32280.1487776614.1@sss.pgh.pa.us> Date: Wed, 22 Feb 2017 10:16:54 -0500 Message-ID: <32281.1487776614@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 isayko.alexey@gmail.com writes: > When using some RE to filter rows on gin-indexed column with pg_trm, > count(*) could give a wrong result (zero instead of real count): Duplicated that here, will look into it. Thanks for the report! regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs