Re: pgsql: Add mem_exceeded_count column to pg_stat_replication_slots. - Mailing list pgsql-committers

From Masahiko Sawada
Subject Re: pgsql: Add mem_exceeded_count column to pg_stat_replication_slots.
Date
Msg-id CAD21AoA8LB+OvmQsp=iOwnBYzPnrVb3jiVMYq1T98NJ5wyec0A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add mem_exceeded_count column to pg_stat_replication_slots.  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-committers
On Wed, Oct 29, 2025 at 1:52 AM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
>
> Hi,
>
> On Wed, Oct 08, 2025 at 05:05:21PM +0000, Masahiko Sawada wrote:
> > Add mem_exceeded_count column to pg_stat_replication_slots.
> >
> > This commit introduces a new column mem_exceeded_count to the
> > pg_stat_replication_slots view. This counter tracks how often the
> > memory used by logical decoding exceeds the logical_decoding_work_mem
> > limit. The new statistic helps users determine whether exceeding the
> > logical_decoding_work_mem limit is a rare occurrences or a frequent
> > issue, information that wasn't available through existing statistics.
> >
> > Bumps catversion.
> >
> > Author: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
> > Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com>
> > Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
> > Reviewed-by: shveta malik <shveta.malik@gmail.com>
> > Reviewed-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
> > Reviewed-by: Chao Li <li.evan.chao@gmail.com>
> > Discussion: https://postgr.es/m/978D21E8-9D3B-40EA-A4B1-F87BABE7868C@yesql.se
>
> I just realized that the discussion mentioned above is not the right one.
> That should be: https://postgr.es/m/aK6zNcmb%2BPpySFvG%40ip-10-97-1-34.eu-west-3.compute.internal
>
> Reporting that here so that the link is not lost.
>

Thank you. That's my fault.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-committers by date:

Previous
From: Álvaro Herrera
Date:
Subject: pgsql: pg_stat_statements: Fix handling of duplicate constant locations
Next
From: Jeff Davis
Date:
Subject: pgsql: Use C11 char16_t and char32_t for Unicode code points.