Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
Date
Msg-id c403a0a0-13b9-4e88-b95b-ba533e0a6988@vondra.me
Whole thread Raw
In response to Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results  (Tomas Vondra <tomas@vondra.me>)
Responses Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
List pgsql-bugs
On 3/19/25 14:43, Tomas Vondra wrote:
>
> ...
> 
> I'll get this fixed shortly. Unfortunately, this means the "bloom"
> filters may be broken - not just those built in parallel, the union
> method can be triggered due to concurrent activity too.
> 

Here's a more complete version of the fix, along with a proper commit
message, etc.

While working on this, I realized there's a second (less severe issue,
in that it fails to free the decompressed filters. I believe this would
be mostly harmless before parallel builds, because we'd merge only one
summary at a time, I think. With parallel builds it may be much worse,
but I'm yet to try how bad.

FWIW I think the minmax-multi has a similar memory leak.

regards

-- 
Tomas Vondra

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible bug acldefault function
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results