Re: Report reorder buffer size - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: Report reorder buffer size
Date
Msg-id CAExHW5sNp7qWg+uteZjh0G_4sDh_Wkyp1AfuXHQ5xsDsV7D4Tg@mail.gmail.com
Whole thread Raw
In response to Re: Report reorder buffer size  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: Report reorder buffer size
List pgsql-hackers
On Mon, Aug 25, 2025 at 6:28 PM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
> > I didn't know this is how it works. Thanks for correcting me. In that
> > case, I think we should
> > add a column in pg_stat_replication_slots reporting the number of
> > times the memory limit is reached since the last reset. I am +0.5 on
> > it being useful.
>
> Thanks. With this in place one could get a ratio like total_txns/total_txns_that_exceeds.
> That could help to see if reaching logical_decoding_work_mem is rare or
> frequent enough. If frequent, then maybe there is a need to adjust logical_decoding_work_mem.
>

We are discussing some improvements to pg_stat_replication_slots over
at [1]. Would you be able to create a patch reporting the number of
times logical_decoding_work_mem is reached, in the patchset being
discussed there?

[1] https://www.postgresql.org/message-id/CAExHW5s6KntzUyUoMbKR5dgwRmdV2Ay_2+AnTgYGAzo=Qv61wA@mail.gmail.com

--
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: shveta malik
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart