Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Naga Appani <nagnrik(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, Xuneng Zhou <xunengzhou(at)gmail(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Date: 2026-09-22 08:00:44
Message-ID: arI1rEHcZKBIiKAo@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2026-09-22 08:05:42 Re: sequencesync worker race with REFRESH SEQUENCES
Previous Message Heikki Linnakangas 2026-09-22 08:00:01 Re: Declare variable-length catalog columns as [] rather than [1]