Re: more descriptive message for process termination due to max_slot_wal_keep_size
От | Drouvot, Bertrand |
---|---|
Тема | Re: more descriptive message for process termination due to max_slot_wal_keep_size |
Дата | |
Msg-id | ddee3c71-4e53-94c8-d823-3cee11c63c07@amazon.com обсуждение исходный текст |
Ответ на | Re: more descriptive message for process termination due to max_slot_wal_keep_size (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Список | pgsql-hackers |
Hi,
On 3/2/22 7:37 AM, Kyotaro Horiguchi wrote:
At Tue, 04 Jan 2022 10:29:31 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote inSo what do you say if I propose the following? LOG: terminating process %d to release replication slot \"%s\" because its restart_lsn %X/%X exceeds the limit %X/%X HINT: You might need to increase max_slot_wal_keep_size.This version emits the following message. [35785:checkpointer] LOG: terminating process 36368 to release replication slot "s1" because its restart_lsn 0/1F000148 exceeds the limit 0/21000000 [35785:checkpointer] HINT: You might need to increase max_slot_wal_keep_size.
As the hint is to increase max_slot_wal_keep_size, what about reporting the difference in size (rather than the limit lsn)? Something along those lines?
[35785:checkpointer] LOG: terminating process 36368 to release replication slot "s1" because its restart_lsn 0/1F000148 exceeds the limit by <NNN MB>.
Regards,
--
Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: