Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
От | Kirill Reshke |
---|---|
Тема | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |
Дата | |
Msg-id | CALdSSPi3Gh08NtcCn44uVeUAYGOT74sU6uei_06qUTa5rMK43g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring (Naga Appani <nagnrik@gmail.com>) |
Список | pgsql-hackers |
On Tue, 11 Mar 2025 at 14:37, Naga Appani <nagnrik@gmail.com> wrote: > > > > On Mon, Mar 10, 2025 at 10:43 AM Naga Appani <nagnrik@gmail.com> wrote: >> >> Hi, >> Hi > ================= > Proposal > ================= > The internal ReadMultiXactCounts() function, implemented in multixact.c, directly calculates the number of MultiXact membersby reading live state from shared memory. This approach avoids the performance issues of the current filesystem-basedestimation 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 MultiXactmember usage. This could be particularly useful for integrating with tools like Amazon RDS Performance Insightsand 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
В списке pgsql-hackers по дате отправления: