Re: Report reorder buffer size
От | Ashutosh Bapat |
---|---|
Тема | Re: Report reorder buffer size |
Дата | |
Msg-id | CAExHW5sNp7qWg+uteZjh0G_4sDh_Wkyp1AfuXHQ5xsDsV7D4Tg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Report reorder buffer size (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>) |
Ответы |
Re: Report reorder buffer size
|
Список | 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 по дате отправления: