From: | Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Keep the decompressed filter in brin_bloom_union |
Date: | 2025-03-26 16:06:02 |
Message-ID: | E1txTGU-00178X-0K@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Keep the decompressed filter in brin_bloom_union
The brin_bloom_union() function combines two BRIN summaries, by merging
one filter into the other. With bloom, we have to decompress the filters
first, but the function failed to update the summary to store the merged
filter. As a consequence, the index may be missing some of the data, and
return false negatives.
This issue exists since BRIN bloom indexes were introduced in Postgres
14, but at that point the union function was called only when two
sessions happened to summarize a range concurrently, which is rare. It
got much easier to hit in 17, as parallel builds use the union function
to merge summaries built by workers.
Fixed by storing a pointer to the decompressed filter, and freeing the
original one. Free the second filter too, if it was decompressed. The
freeing is not strictly necessary, because the union is called in
short-lived contexts, but it's tidy.
Backpatch to 14, where BRIN bloom indexes were introduced.
Reported by Arseniy Mukhin, investigation and fix by me.
Reported-by: Arseniy Mukhin
Discussion: https://postgr.es/m/18855-1cf1c8bcc22150e6%40postgresql.org
Backpatch-through: 14
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/818245506c285e0325141dabb1ced45057937502
Modified Files
--------------
src/backend/access/brin/brin_bloom.c | 11 +++++++++++
1 file changed, 11 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2025-03-26 16:06:12 | pgsql: Keep the decompressed filter in brin_bloom_union |
Previous Message | Tom Lane | 2025-03-26 15:11:32 | pgsql: Introduce PG_MODULE_MAGIC_EXT macro. |