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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Naga Appani <nagnrik(at)gmail(dot)com>
Cc: 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
Subject: Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Date: 2025-12-30 07:44:03
Message-ID: aVOCw5ANG4Tk2C55@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 29, 2025 at 08:57:11PM -0600, Naga Appani wrote:
> The oldest_multixact correctly advances to reflect the cleanup.
>
> Thanks for adding the pg_read_all_stats privilege check!
>
> I think this is ready for RFC.

Thanks for looking. I have done an extra round of brush-up, then
applied the set. The buildfarm looks OK with it.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2025-12-30 08:01:26 Re: RFC: PostgreSQL Storage I/O Transformation Hooks
Previous Message Alena Vinter 2025-12-30 07:34:21 Re: Resetting recovery target parameters in pg_createsubscriber