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 1n4YxQ-0002q6-Pv for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Jan 2022 01:49:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n4YxO-0006xI-JU for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Jan 2022 01:49:46 +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 1n4YxO-0006x8-8X for pgsql-hackers@lists.postgresql.org; Tue, 04 Jan 2022 01:49:46 +0000 Received: from mail-pf1-x430.google.com ([2607:f8b0:4864:20::430]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n4YxL-0000Pe-TU for pgsql-hackers@lists.postgresql.org; Tue, 04 Jan 2022 01:49:45 +0000 Received: by mail-pf1-x430.google.com with SMTP id b22so30815593pfb.5 for ; Mon, 03 Jan 2022 17:49:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=8jPMViLyDZlbRiAnVa29tKTeXg9rjuMuWZEMbY+V+UY=; b=LwJ78fcjCZDBkD3kiEGxDe3XmmO+BZo1qJsXBMqCvM/56HO6z2rsPAdFBYldxST+DX KeKfi+EDpAZuRG7oW8UEt285cZW2nqp6PZeLzmRuqafsM2stp8/rb4T2MwVQ6tf46xmu gjOAcEgt5mSEGEw37395Hu8fD//jczG+VKCHGbqiTWTPRFYQrdJnVAkmUs9A+rtNljv5 5ENNPc0jeum6SlKf/79R+x2g2jke0X1yZFRRFxphehmjG77sXlXvVkjyNXnB+kZWd3iV TgcjgffaDA1RXQkBGLpM3vkuCNjs3xpKsuUx1TZh66D1r7VKQkmY0RKWHVeLtMFR7UOu QJKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=8jPMViLyDZlbRiAnVa29tKTeXg9rjuMuWZEMbY+V+UY=; b=upIGS4PpMnZANk2orpiYyJ+9tyFH4R+GeROJbcU/krOSVm6zm74mf6E9S9hoKAjeT1 sCTxaW4iqL6KVjajozydEvGaQlpRxcxKP2CtW50Haw8WTl0bkR4YvkX+uqpQrSXgP4WG swaMEfp/1RDjiOAiw0OqJG+hZNEfzl8Q7jA50ayWsO6EKma2knNPHR2yOEEKwKQZ5wzP jfo1UtWvl+rv/krbUerP9gy0yZ6HTpCrwvx9QrCGkwsNGVhHYM1AeWH07MCJPR1Dgjtq ZfFDvmGlk5PmqALpTOpgR/y59z4qyB7c4v64KY/Ex+SbgLKQ63+kRwPeeOQfT5HqQKo3 N05A== X-Gm-Message-State: AOAM533MPDgp68mm/bbmMul7pircx2i4N8Xf92ZXJK0iqcqcrAx8Cv9t d/YGNb8Z0ZF0zAK5gM/JIW0= X-Google-Smtp-Source: ABdhPJyxOEqNxNeaD3+d6oGDToBzLOTOUXo9ZzK1N0b5yZN2yp0kNf2DJihWXhHJmd53Jfw86d45PQ== X-Received: by 2002:aa7:96c5:0:b0:4ba:55c0:5e12 with SMTP id h5-20020aa796c5000000b004ba55c05e12mr48802057pfq.86.1641260981672; Mon, 03 Jan 2022 17:49:41 -0800 (PST) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id pf7sm42460414pjb.8.2022.01.03.17.49.39 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Mon, 03 Jan 2022 17:49:40 -0800 (PST) Date: Tue, 04 Jan 2022 10:49:38 +0900 (JST) Message-Id: <20220104.104938.1202548681429146328.horikyota.ntt@gmail.com> To: bharath.rupireddyforpostgres@gmail.com Cc: michael@paquier.xyz, pgsql-hackers@lists.postgresql.org Subject: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message From: Kyotaro Horiguchi In-Reply-To: References: User-Agent: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk At Tue, 28 Dec 2021 08:26:28 +0530, Bharath Rupireddy wrote in > On Fri, Dec 24, 2021 at 5:54 PM Bharath Rupireddy > wrote: > > > > On Fri, Dec 24, 2021 at 5:42 PM Michael Paquier wrote: > > > > > > On Fri, Dec 24, 2021 at 02:51:34PM +0900, Kyotaro Horiguchi wrote: > > > > I thougt about something like the following, but your proposal may be > > > > clearer. > > > > > > + "LSN=%X/%X, REDO LSN=%X/%X", > > > This could be rather confusing for the average user, even if I agree > > > that this is some information that only an advanced user could > > > understand. Could it be possible to define those fields in a more > > > deterministic way? For one, it is hard to understand the relationship > > > between both fields without looking at the code, particulary if both > > > share the same value. It is at least rather.. Well, mostly, easy to > > > guess what each other field means in this context, which is not the > > > case of what you are proposing here. One idea could be use also > > > "start point" for REDO, for example. > > > > How about "location=%X/%X, REDO start location=%X/%X"? The entire log > > message can look like below: .. > Thoughts? It seems to me "LSN" or just "location" is more confusing or mysterious than "REDO LSN" for the average user. If we want to avoid being technically too detailed, we would use just "start LSN=%X/%X, end LSN=%X/%X". And it is equivalent to "WAL range=[%X/%X, %X/%X]".. regards. -- Kyotaro Horiguchi NTT Open Source Software Center