Re: pg_get_multixact_members not documented

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(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 13:25:37
Message-ID: aGKQUXM_ROke5xe6@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 30, 2025 at 04:08:04PM +0300, Sami Imseih wrote:
> Correct, I originally proposed the "Transaction ID and Snapshot
> Information Functions" section, but as stated in [0],
> pg_get_multixact_members does not fit the description of the section as
> it is described as "The main use of these functions is to determine
> which transactions were committed between two snapshots."

Well, is that description correct? I've used several of these functions,
but I'm not sure I've ever used them for this purpose.

Looking again, pg_get_multixact_members() might need to be added to this
list of exceptions:

However, the functions shown in Table 9.84, except age and mxid_age,
use a 64-bit type xid8 that does not wrap around during the life of an
installation and can be converted to xid by casting if required; see
Section 67.1 for details.

I'm also a little wary of adding a new section on the back-branches because
it will change some section numbers.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou (Fujitsu) 2025-06-30 13:28:35 RE: Conflict detection for update_deleted in logical replication
Previous Message Melanie Plageman 2025-06-30 13:20:33 Re: Periodic FSM vacuum doesn't happen in one-pass strategy vacuum.