Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q9z86-0005M4-Ps for pgsql-bugs@arkaria.postgresql.org; Fri, 16 Jun 2023 02:24:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q9z85-0000yV-PS for pgsql-bugs@arkaria.postgresql.org; Fri, 16 Jun 2023 02:24:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q9z85-0000yL-I2 for pgsql-bugs@lists.postgresql.org; Fri, 16 Jun 2023 02:24:01 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q9z81-002S7q-6v for pgsql-bugs@lists.postgresql.org; Fri, 16 Jun 2023 02:23:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 35G2NqTu2322241; Thu, 15 Jun 2023 22:23:52 -0400 From: Tom Lane To: Masahiko Sawada cc: exclusion@gmail.com, Tomas Vondra , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25 In-reply-to: References: <17969-a6c54de48026d694@postgresql.org> <836412.1686502986@sss.pgh.pa.us> Comments: In-reply-to Masahiko Sawada message dated "Fri, 16 Jun 2023 11:18:30 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2322239.1686882232.1@sss.pgh.pa.us> Date: Thu, 15 Jun 2023 22:23:52 -0400 Message-ID: <2322240.1686882232@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Masahiko Sawada writes: > It seems that the minimum false positive rate also doesn't work: > postgres(1:3419179)=# create table t (a int); > CREATE TABLE > postgres(1:3419179)=# create index t_idx on t using brin (a > int4_bloom_ops (false_positive_rate = 0.0001)); > CREATE INDEX > postgres(1:3419179)=# insert into t values (1); > 2023-06-16 11:14:01.349 JST [3419179] ERROR: the bloom filter is too > large (8924 > 8144) > 2023-06-16 11:14:01.349 JST [3419179] STATEMENT: insert into t values (1); > ERROR: the bloom filter is too large (8924 > 8144) Hmm, but it would work with a larger page size, right? If so I'm disinclined to move the minimum. What I don't like about the above is that the failure doesn't occur until you actually insert an index entry. Is there a way to check for this at CREATE INDEX time? regards, tom lane