Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: exclusion@gmail.com, Tomas Vondra <tomas.vondra@enterprisedb.com>,
pgsql-bugs@lists.postgresql.org
Date: 2023-06-16T02:23:52Z
Lists: pgsql-bugs
Masahiko Sawada <sawada.mshk@gmail.com> 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
Commits
-
Enlarge assertion in bloom_init() for false_positive_rate
- 59fc39c0d5d9 14.11 landed
- 7e18c0bd63ae 15.6 landed
- 4dccf9575369 16.2 landed
- 1b2c6b756eaa 17.0 landed