Re: more descriptive message for process termination due to max_slot_wal_keep_size
Drouvot, Bertrand <bdrouvot@amazon.com>
From: "Drouvot, Bertrand" <bdrouvot@amazon.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, <sawada.mshk@gmail.com>
Cc: <ashutosh.bapat.oss@gmail.com>, <pgsql-hackers@postgresql.org>
Date: 2022-09-05T09:56:33Z
Lists: 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 in >> So 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
Commits
-
Improve wording of log messages triggered by max_slot_wal_keep_size.
- 551aa6b7b9f3 16.0 landed