| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 |
| Subject: | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |
| Date: | 2026-09-21 15:30:54 |
| Message-ID: | yhtrliiq662vmhqy2xnbg67ezrucmwtfuuus2zcjvmwgmracux@2cqaioxnntwz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-12-30 16:44:03 +0900, Michael Paquier wrote:
> 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.
I didn't know where else to ask:
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?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2026-09-21 15:35:35 | Re: Reduce cleanup lock contention on standby replay |
| Previous Message | Kiran Kaki | 2026-09-21 15:29:34 | Re: pg_walinspect: fix LSN validation messages and empty range handling |