Re: more descriptive message for process termination due to max_slot_wal_keep_size

From: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, <sawada(dot)mshk(at)gmail(dot)com>
Cc: <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: more descriptive message for process termination due to max_slot_wal_keep_size
Date: 2022-09-05 09:56:33
Message-ID: ddee3c71-4e53-94c8-d823-3cee11c63c07@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(dot)ntt(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-09-05 10:12:16 Re: TRAP: FailedAssertion("prev_first_lsn < cur_txn->first_lsn", File: "reorderbuffer.c", Line: 927, PID: 568639)
Previous Message Zhihong Yu 2022-09-05 09:50:09 Re: freeing LDAPMessage in CheckLDAPAuth