Re: Small and unlikely overflow hazard in bms_next_member() - Mailing list pgsql-hackers

From David Rowley
Subject Re: Small and unlikely overflow hazard in bms_next_member()
Date
Msg-id CAApHDvoTeKuo+bs2g8UXbZ9jDvbEURPFAaCaXfEm+2Xmc5i9qw@mail.gmail.com
Whole thread Raw
In response to Re: Small and unlikely overflow hazard in bms_next_member()  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On Mon, 13 Apr 2026 at 12:24, Chao Li <li.evan.chao@gmail.com> wrote:
> I just tried test_bms_next3 on my MacBook, looks like patched bms_prev_member is much faster there. I ran about 10
times,the results were consistent.
 

Thanks. I saw similar results.

David



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Bug: Rule actions see wrong values for generated columns (NEW.gen reads OLD value)
Next
From: Chao Li
Date:
Subject: Re: quoteOneName() inconsistency with quote_all_identifiers — replacement API proposed