Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oV92K-0007IX-VT for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Sep 2022 10:09:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oV92J-0005Q1-Ij for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Sep 2022 10:08:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oV92I-0005Ps-Qe for pgsql-hackers@lists.postgresql.org; Mon, 05 Sep 2022 10:08:59 +0000 Received: from smtp-fw-80007.amazon.com ([99.78.197.218]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oV92G-0002QE-Ic for pgsql-hackers@postgresql.org; Mon, 05 Sep 2022 10:08:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1662372536; x=1693908536; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to; bh=bWMajm71sP/sMelF3wxpnfoX8IW07DqtknDHgYIeACE=; b=UMtBHHkzZuhrpw79l0YXcXIh0In/UlJicHwMdoxxPJ+buxWlGgOxjwTQ CKhcdZ8oE5YzZiWZ1Vz0SoAae628cOIH0qJ+OD4ro+IRNejhNe8PsOPZ6 g/hLtfJnFb7EK/okuA8jo/Su0GO4YPnwD9uruGQNFiD0rvi8yjcW157sI M=; X-IronPort-AV: E=Sophos;i="5.93,290,1654560000"; d="scan'208,217";a="126837463" Received: from pdx4-co-svc-p1-lb2-vlan3.amazon.com (HELO email-inbound-relay-iad-1a-4ba5c7da.us-east-1.amazon.com) ([10.25.36.214]) by smtp-border-fw-80007.pdx80.corp.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2022 09:56:37 +0000 Received: from EX13D03EUC003.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan2.iad.amazon.com [10.40.163.34]) by email-inbound-relay-iad-1a-4ba5c7da.us-east-1.amazon.com (Postfix) with ESMTPS id E4EFB8FAED; Mon, 5 Sep 2022 09:56:35 +0000 (UTC) Received: from [192.168.25.173] (10.43.166.207) by EX13D03EUC003.ant.amazon.com (10.43.164.192) with Microsoft SMTP Server (TLS) id 15.0.1497.38; Mon, 5 Sep 2022 09:56:34 +0000 Content-Type: multipart/alternative; boundary="------------vhwOsBJbyCTmwPangVerC4Px" Message-ID: Date: Mon, 5 Sep 2022 11:56:33 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.0.2 Subject: Re: more descriptive message for process termination due to max_slot_wal_keep_size Content-Language: en-US To: Kyotaro Horiguchi , CC: , References: <20211224.173016.2237752923975758130.horikyota.ntt@gmail.com> <20220104.102931.1400105396066285349.horikyota.ntt@gmail.com> <20220302.153719.171492355527427161.horikyota.ntt@gmail.com> From: "Drouvot, Bertrand" In-Reply-To: <20220302.153719.171492355527427161.horikyota.ntt@gmail.com> X-Originating-IP: [10.43.166.207] X-ClientProxiedBy: EX13D49EUC002.ant.amazon.com (10.43.164.112) To EX13D03EUC003.ant.amazon.com (10.43.164.192) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --------------vhwOsBJbyCTmwPangVerC4Px Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Hi, On 3/2/22 7:37 AM, Kyotaro Horiguchi wrote: > At Tue, 04 Jan 2022 10:29:31 +0900 (JST), Kyotaro Horiguchi 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 . Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services:https://aws.amazon.com --------------vhwOsBJbyCTmwPangVerC4Px Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit

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
--------------vhwOsBJbyCTmwPangVerC4Px--