Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Date
Msg-id arG3RW2R3qsIj5zJ@paquier.xyz
Whole thread
In response to Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring  (Andres Freund <andres@anarazel.de>)
Responses Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
List pgsql-hackers
On Mon, Sep 21, 2026 at 11:30:54AM -0400, Andres Freund wrote:
> I didn't know where else to ask:

That sounds like the correct place to me.  :D

> Why is pg_get_multixact_stats() called _stats? From what I can tell it doesn't
> return anything stats like? What it returns is more like the *state* of the
> subsystem?

Hmm.  Perhaps pg_get_multixact_state() then?  We still have time to
adjust that before the release.  If somebody has a better idea of
name, please feel free.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity
Next
From: Sami Imseih
Date:
Subject: Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring