Re: pg_get_multixact_members not documented - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: pg_get_multixact_members not documented
Date
Msg-id CAExHW5u9Kz4E3jMX=EUChW2XGx862CXw5XT2VejwHXhPK810tA@mail.gmail.com
Whole thread Raw
In response to Re: pg_get_multixact_members not documented  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: pg_get_multixact_members not documented
List pgsql-hackers
On Sat, Jun 28, 2025 at 4:02 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> On Thu, Jun 12, 2025 at 03:10:56PM -0500, Nathan Bossart wrote:
> > Barring comments/objections, I'll plan on committing/back-patching this in
> > the near future.
>
> Here is what I have staged for commit.  I ended up moving it to the
> "Transaction ID and Snapshot Information Functions" table, which is what I
> think you had originally proposed.  Creating a new section for this seemed
> unnecessary, and this table already has one multixact-related function.

WFM.


--
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages
Next
From: Michael Paquier
Date:
Subject: Re: Addition of %b/backend_type in log_line_prefix of TAP test logs