MIME-Version: 1.0
References: 
 <CA+QeY+AAsYK6WvBW4qYzHz4bahHycDAY_q5ECmHkEV_eB9ckzg@mail.gmail.com>
 <CA+QeY+CuTcKSFmw3H-_OtCv+bv0T4uTSFgaAY1N9ssL-WaiiSA@mail.gmail.com>
In-Reply-To: 
 <CA+QeY+CuTcKSFmw3H-_OtCv+bv0T4uTSFgaAY1N9ssL-WaiiSA@mail.gmail.com>
From: Kirill Reshke <reshkekirill@gmail.com>
Date: Tue, 11 Mar 2025 14:48:01 +0500
Message-ID: 
 <CALdSSPi3Gh08NtcCn44uVeUAYGOT74sU6uei_06qUTa5rMK43g@mail.gmail.com>
Subject: Re: [Proposal] Expose internal MultiXact member count function for
 efficient monitoring
To: Naga Appani <nagnrik@gmail.com>
Cc: pgsql-hackers@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CALdSSPi3Gh08NtcCn44uVeUAYGOT74sU6uei_06qUTa5rMK43g%40mail.gmail.com>
Precedence: bulk

On Tue, 11 Mar 2025 at 14:37, Naga Appani <nagnrik@gmail.com> wrote:
>
>
>
> On Mon, Mar 10, 2025 at 10:43=E2=80=AFAM Naga Appani <nagnrik@gmail.com> =
wrote:
>>
>> Hi,
>>

Hi

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Proposal
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> The internal ReadMultiXactCounts() function, implemented in multixact.c, =
directly calculates the number of MultiXact members by reading live state f=
rom shared memory. This approach avoids the performance issues of the curre=
nt 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 Postgr=
eSQL users with an efficient way to monitor MultiXact member usage. This co=
uld be particularly useful for integrating with tools like Amazon RDS Perfo=
rmance 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=E2=80=99ll go ahe=
ad and submit a patch.

Let's give it a try!


--=20
Best regards,
Kirill Reshke