Re: pg_get_multixact_members not documented

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_get_multixact_members not documented
Date: 2025-06-02 20:33:03
Message-ID: CAA5RZ0vtSPzx+8HW1gohcWPgURX2VST5j3Nqh2OL6h9dSk0HSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--
Sami Imseih
Amazon Web Services (AWS)

On Mon, Jun 2, 2025 at 3:03 PM Nathan Bossart <nathandbossart(at)gmail(dot)com>
wrote:

> On Mon, Jun 02, 2025 at 12:46:51PM -0500, Sami Imseih wrote:
> > v1-0001 is the documentation only patch. I improved upon the description
> > suggested in [0]
>
> Your patch adds an entry to the "Transaction ID and Snapshot Information
> Functions" table, while Álvaro's introduced a new "Multixact Functions"
> table. His also added a note to maintenance.sgml. Any reason for the
> differences?

My initial thoughts were to add a new section,
but was not sure if it made sense since there
will only be a single function. Well, that’s not a good
reason and we may add some more in the future.

Also, the “Transaction ID and Snapshot Function” section is
probably the wrong section because the mxid’s/xid’s may
not have been committed. So I will correct. I will also add
a reference In maintenance.sgml


Sami

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Borisov 2025-06-02 21:51:08 Improve the performance of Unicode Normalization Forms.
Previous Message Peter Geoghegan 2025-06-02 20:05:51 Re: Correcting freeze conflict horizon calculation