Re: pg_get_multixact_members not documented

On Wed, Jun 11, 2025 at 9:44 PM Sami Imseih <samimseih(at)gmail(dot)com> wrote:

> > It's not clear, without some effort, which lock mode go with which row
> lock in that description.
> > For example, "keysh" does not have "for" in it but "fornokeyupd" does.
> How about rephrasing this
> > as "The lock modes "keysh", "sh", fornokeyupd", and "forupd" correspond
> to
> > <literal>FOR KEY SHARE</literal>, <literal>FOR SHARE</literal>,
> <literal>FOR NO KEY UPDATE</literal>,
> > and <literal>FOR UPDATE</literal> row level locks respectively as
> described in <xref linkend="locking-rows"/>."
>
> That works for me.
>
> > Do we want to add the section "Multixact Information Functions" after
> other transaction related
> > sections like "Transaction ID and Snapshot Information Function" and
> > " Committed Transaction Information Functions" instead of adding it at
> the end?
>
> makes sense.
>
>
Attached patch removing extra comma. Otherwise LGTM.

Please add the patch to CF, if not already done and mark it as "ready for
committer".

--
Best Wishes,
Ashutosh Bapat