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

From Sami Imseih
Subject Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Date
Msg-id CAN12+YKc278ayOBzF4Rbosrz=5QzRJ7t7bHff-FKiJbbvgwFzg@mail.gmail.com
Whole thread
In response to Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
List pgsql-hackers
> > 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.

I guess pg_get_multixact_usage() sounds better to me and it matches the
code comment:

/*
 * pg_get_multixact_stats
 *
 * Returns statistics about current multixact usage.
 */

--
Sami



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Next
From: shihao zhong
Date:
Subject: Re: REPACK enhancements