Re: pg_get_multixact_members not documented

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_get_multixact_members not documented
Date: 2025-06-30 04:29:23
Message-ID: CAExHW5u9Kz4E3jMX=EUChW2XGx862CXw5XT2VejwHXhPK810tA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 28, 2025 at 4:02 AM Nathan Bossart <nathandbossart(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daisuke Higuchi 2025-06-30 04:44:58 Typo in pg_stat_activity definition
Previous Message vignesh C 2025-06-30 04:13:11 Re: pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 pages