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 CAApHDvpVKtgtNsXXKECi4KhzH3JpN2k62tg=EcYmsEA+RsKj+A@mail.gmail.com
Whole thread
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, 6 Apr 2026 at 14:01, Chao Li <li.evan.chao@gmail.com> wrote:
> > On Apr 4, 2026, at 11:30, David Rowley <dgrowleyml@gmail.com> wrote:
> > Not quite perfect as a set made first as a single word set that later
> > becomes a multi-word set will be double counted. The number of
> > operations on the sets is likely more important anyway, not the number
> > of sets being created. The point is, multi-word sets are rare for most
> > workloads.
> >
>
> What tests did you run after adding the logs to collect the data? This is a method I might borrow in the future for
similarinvestigations.
 

"make check" then grep regression.diffs for the NOTICE message and
pipe to "wc -l"



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Non-compliant SASLprep implementation for ASCII characters
Next
From: Alexander Lakhin
Date:
Subject: Re: Non-compliant SASLprep implementation for ASCII characters