Request a Demo
Home   >   mailing lists

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

From Melanie Plageman
Subject Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Date
Msg-id CAAKRu_bE11PUHDVthMoKXownefkzB8H31WLTvq2XXy5WgJsTxg@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
List pgsql-hackers
Tree view 
On Tue, Sep 22, 2026 at 4:01 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Sep 21, 2026 at 06:22:35PM -0500, Sami Imseih wrote:
> > I guess pg_get_multixact_usage() sounds better to me and it matches the
> > code comment:
>
> That would be OK here.  CC-ing Nathan for RMT input, as this would
> require a catversion bump.

I don't have an issue with a catversion bump as long as it's before GA
and it doesn't make it more likely we'll have to change it again after
GA.


- Melanie

pgsql-hackers by date:

Previous
From: Zhijie Hou
Date:
Subject: Re: sequencesync worker race with REFRESH SEQUENCES
Next
From: Bertrand Drouvot
Date:
Subject: Re: Add a permission check to pg_stat_get_backend_subxact()