Re: Possible api miuse bms_next_member - Mailing list pgsql-hackers

From David Rowley
Subject Re: Possible api miuse bms_next_member
Date
Msg-id CAApHDvpp1AczfpRToawJ1xNoExtFXQbfpPueOuPtjP5xauRc9Q@mail.gmail.com
Whole thread Raw
In response to Re: Possible api miuse bms_next_member  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 10 Apr 2025 at 02:18, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> If we did want to do something about this warning, rather than
> hacking up the call sites I'd be inclined to invent something like
> "bms_first_member()" which does the same thing but additionally
> asserts on empty input.  Not really convinced it's worth the
> trouble though.

Aha, a reincarnation! (462bb7f12).

My vote too is to do nothing.

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Thomas Munro
Date:
Subject: Re: BitmapHeapScan streaming read user and prelim refactoring