From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
---|---|
To: | Naga Appani <nagnrik(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |
Date: | 2025-03-11 09:48:01 |
Message-ID: | CALdSSPi3Gh08NtcCn44uVeUAYGOT74sU6uei_06qUTa5rMK43g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 11 Mar 2025 at 14:37, Naga Appani <nagnrik(at)gmail(dot)com> wrote:
>
>
>
> On Mon, Mar 10, 2025 at 10:43 AM Naga Appani <nagnrik(at)gmail(dot)com> wrote:
>>
>> Hi,
>>
Hi
> =================
> Proposal
> =================
> The internal ReadMultiXactCounts() function, implemented in multixact.c, directly calculates the number of MultiXact members by reading live state from shared memory. This approach avoids the performance issues of the current filesystem-based estimation methods.
This proposal looks sane. It is indeed helpful to keep an eye out for
multixact usage in systems that are heavily loaded.
> By exposing ReadMultiXactCounts() for external use, we can provide PostgreSQL users with an efficient way to monitor MultiXact member usage. This could be particularly useful for integrating with tools like Amazon RDS Performance Insights and Amazon CloudWatch to provide enhanced database insights and proactive managed monitoring for users.
>
> Please let me know if this approach is acceptable, so I’ll go ahead and submit a patch.
Let's give it a try!
--
Best regards,
Kirill Reshke
From | Date | Subject | |
---|---|---|---|
Next Message | Ilia Evdokimov | 2025-03-11 09:58:06 | Re: explain analyze rows=%.0f |
Previous Message | Bykov Ivan | 2025-03-11 09:47:18 | RE: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET |