From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
---|---|
To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Report reorder buffer size |
Date: | 2025-08-26 09:26:14 |
Message-ID: | CAExHW5sNp7qWg+uteZjh0G_4sDh_Wkyp1AfuXHQ5xsDsV7D4Tg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 25, 2025 at 6:28 PM Bertrand Drouvot
<bertranddrouvot(dot)pg(at)gmail(dot)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?
--
Best Wishes,
Ashutosh Bapat
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2025-08-26 09:30:24 | Re: [BUG] Remove self joins causes 'variable not found in subplan target lists' error |
Previous Message | Dilip Kumar | 2025-08-26 09:02:10 | Re: Conflict detection for update_deleted in logical replication |