Re: more descriptive message for process termination due to max_slot_wal_keep_size
От | Tom Lane |
---|---|
Тема | Re: more descriptive message for process termination due to max_slot_wal_keep_size |
Дата | |
Msg-id | 332715.1664472660@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: more descriptive message for process termination due to max_slot_wal_keep_size (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: more descriptive message for process termination due to max_slot_wal_keep_size
|
Список | pgsql-hackers |
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes: > At Wed, 28 Sep 2022 16:30:37 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in >> I think you should leave the primary message alone and add a DETAIL, >> as the first version of the patch did. > So I'm going to change the mssage as: > LOG: terminating process %d to release replication slot \"%s\" > DETAIL: The slot's restart_lsn %X/%X exceeds the limit by %lld bytes. > HINT: You might need to increase max_slot_wal_keep_size. > LOG: invalidating *replication* slot \"%s\" > DETAILS: (ditto) > HINTS: (ditto) I thought the latter was a little *too* short; the primary message should at least give you some clue why that happened, even if it doesn't offer all the detail. After some thought I changed it to LOG: invalidating obsolete replication slot \"%s\" and pushed it that way. regards, tom lane
В списке pgsql-hackers по дате отправления: