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 1oWDrD-0008FF-3B for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Sep 2022 09:29:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oWDrB-0007dT-VQ for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Sep 2022 09:29:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWDrB-0007dJ-G1 for pgsql-hackers@lists.postgresql.org; Thu, 08 Sep 2022 09:29:57 +0000 Received: from smtp-fw-6001.amazon.com ([52.95.48.154]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWDr7-0004ba-N4 for pgsql-hackers@postgresql.org; Thu, 08 Sep 2022 09:29:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1662629394; x=1694165394; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to; bh=BfhMmVSBpaQ3s0aky8ECRyevlRrA2adDX1la1IaA3R0=; b=C34cq+nOH0or2n14oVabAZOOjrY7U2JbasrjCtHs9ohsdpUTdlRUGU0c 92k43t7+XHTzgUnGpZPYaTjDvpp8qzp3w2RPZ/wt/1n8/JVNQMlz5IzzU l9myZydVradsWhZR+cRzan1JOflNtSjV2tQS5H4nQzBDn4pXRoScXAxYX o=; Received: from iad12-co-svc-p1-lb1-vlan2.amazon.com (HELO email-inbound-relay-iad-1e-54c9d11f.us-east-1.amazon.com) ([10.43.8.2]) by smtp-border-fw-6001.iad6.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Sep 2022 09:29:41 +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-1e-54c9d11f.us-east-1.amazon.com (Postfix) with ESMTPS id 7A344C08A2; Thu, 8 Sep 2022 09:29:40 +0000 (UTC) Received: from [192.168.1.123] (10.43.165.87) by EX13D03EUC003.ant.amazon.com (10.43.164.192) with Microsoft SMTP Server (TLS) id 15.0.1497.38; Thu, 8 Sep 2022 09:29:39 +0000 Content-Type: multipart/alternative; boundary="------------hWizscBYso0iNdiGCV9AGB6A" Message-ID: <09df1227-4f6f-6b4e-1503-697fd110bb9d@amazon.com> Date: Thu, 8 Sep 2022 11:29:38 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.2.1 Subject: Re: more descriptive message for process termination due to max_slot_wal_keep_size Content-Language: en-US To: Kyotaro Horiguchi CC: , , References: <03ee95c3-6496-90b7-5c8b-13fe69ee73dd@amazon.com> <20220907.112019.758274712731312487.horikyota.ntt@gmail.com> <95534909-b8a0-d447-b940-b91006397962@amazon.com> <20220908.134020.228552226800754222.horikyota.ntt@gmail.com> From: "Drouvot, Bertrand" In-Reply-To: <20220908.134020.228552226800754222.horikyota.ntt@gmail.com> X-Originating-IP: [10.43.165.87] X-ClientProxiedBy: EX13D30EUC004.ant.amazon.com (10.43.164.11) 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 --------------hWizscBYso0iNdiGCV9AGB6A Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Hi, On 9/8/22 6:40 AM, Kyotaro Horiguchi wrote: > At Wed, 7 Sep 2022 12:16:29 +0200, "Drouvot, Bertrand" wrote in >>>> LOG: terminating process 49539 to release replication slot "rep1" >>>> because its restart_lsn 0/3038000 exceeds the limit by 15.8 MB >>> If the distance were 1 byte, it is shown as "0.1 MB". >> Right and I'm -1 on it, I think we should stick to the "pretty" or the >> "bytes only" approach (my preference being the bytes only one). > Okay. the points you brought up above are sufficient grounds for not > doing so. Now they are in the following format. > >>> LOG: terminating process 16034 to release replication slot "rep1" >>> because its restart_lsn 0/3158000 exceeds the limit by 15368192 bytes > Thank you for the discussion, Bertrand! You are welcome, thanks for the patch! It looks good to me, barring any objections i think we can mark the CF entry as Ready for Committer. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services:https://aws.amazon.com --------------hWizscBYso0iNdiGCV9AGB6A Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit

Hi,

On 9/8/22 6:40 AM, Kyotaro Horiguchi wrote:
At Wed, 7 Sep 2022 12:16:29 +0200, "Drouvot, Bertrand" <bdrouvot@amazon.com> wrote in
LOG: terminating process 49539 to release replication slot "rep1"
because its restart_lsn 0/3038000 exceeds the limit by 15.8 MB
If the distance were 1 byte, it is shown as "0.1 MB".
Right and I'm -1 on it, I think we should stick to the "pretty" or the
"bytes only" approach (my preference being the bytes only one).
Okay. the points you brought up above are sufficient grounds for not
doing so.  Now they are in the following format.

LOG: terminating process 16034 to release replication slot "rep1"
because its restart_lsn 0/3158000 exceeds the limit by 15368192 bytes
Thank you for the discussion, Bertrand!

You are welcome, thanks for the patch!

It looks good to me, barring any objections i think we can mark the CF entry as Ready for Committer.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
--------------hWizscBYso0iNdiGCV9AGB6A--