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 1nDKv9-0001sm-Pi for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Jan 2022 06:39:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nDKv8-0003X1-HZ for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Jan 2022 06:39:42 +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 1nDKv8-0003Ws-71 for pgsql-hackers@lists.postgresql.org; Fri, 28 Jan 2022 06:39:42 +0000 Received: from mail-pg1-x536.google.com ([2607:f8b0:4864:20::536]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nDKv6-0003Ph-2K for pgsql-hackers@lists.postgresql.org; Fri, 28 Jan 2022 06:39:41 +0000 Received: by mail-pg1-x536.google.com with SMTP id j10so4406809pgc.6 for ; Thu, 27 Jan 2022 22:39:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zopWygxURs1LB0saPzQlBa6wFAi+xH56ewg7EQnuFC0=; b=BV6gKrT0W5WzA+Vys6wD8eHesJIfN0ZHwQj4wtOmhuSBOf/ZYJDCjESKoKfzYt6wAF yHYbICxB7+EBRXkotpHxuBrPK+IHKsskJZAfgl4S/pDZg/4iwLA3V0IlA/u3n+3zVjLG +vyTQm7bltIRSOJd2RGF8IzeRMNobbbvWXFjNf3sryA2/4H+Lk/kKRMIgM8wYRBoDasA EwLEjKPSP+hdmJYsuTOY6IzzgcI58QD48UxLrBDTvBhxcqz+Cc78Sps4PxOgrXKhvE9V Jz137ynRat2DAohiFRQKeHbMw69gvU+pV0Qwd/0lbwUMcDJUu3bREep9+Go1kdwyp/YX so8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zopWygxURs1LB0saPzQlBa6wFAi+xH56ewg7EQnuFC0=; b=jExg3G1hRWmZJyzcGGdOMKIBUL4nLnFwuviqrPSLr0xIhCQxGWsC4+eRPEOFQAUPdz KtRPI7Pwh2TN+cGSJ/6SWQYLNoH9i0n02esJau4FwTArU3MGgEXvqp4AWWZq1K7o3eZM WF0cnsXW0EFx60qYrUFiQu1Oo4oW6IiQ832mxymhsE1IpW2KD2BDnQHWb4X62Jw+RNw0 cTFJQzuTiVc5NlJrnfUPSsR1qkQe1xp5sRi77dPH2Yx3lgYBr6eIhSXMqUKvF5bsBg/l P28C8xbwuGBsdBaaL+J1BPnngykjSx4H6/VS4yv5tsiMbaa+5IRWV0bymb1viBiey70n hpwA== X-Gm-Message-State: AOAM530og9+tBBJzkCGwLE+es2p+FqJzqWcLAjKdcYYdeHqWm6ZheSrO aInZ1GIGrgTE0Iq9w/Ife8rABQqA+cliTNmbFAA= X-Google-Smtp-Source: ABdhPJyfHkRyAQKk+bEaxeUblXRGhB7VPBKfZ4qHSj2cOXW42REFRFAsWkX0FQskMzuQP924sXoGPtgco1vDxciAJEU= X-Received: by 2002:aa7:8e89:: with SMTP id a9mr7071334pfr.64.1643351978939; Thu, 27 Jan 2022 22:39:38 -0800 (PST) MIME-Version: 1.0 References: <20220120.120029.1092463916382268628.horikyota.ntt@gmail.com> <20220128054620.GA654866@nathanxps13> In-Reply-To: <20220128054620.GA654866@nathanxps13> From: Bharath Rupireddy Date: Fri, 28 Jan 2022 12:09:28 +0530 Message-ID: Subject: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message To: Nathan Bossart Cc: Kyotaro Horiguchi , "Bossart, Nathan" , Julien Rouhaud , Michael Paquier , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 28, 2022 at 11:16 AM Nathan Bossart wrote: > > I know I voted for "start=3D%X/%X, end=3D%X/%X," but looking at this agai= n, I > wonder if it could be misleading. "start" is the redo location, and "end= " > is the location of the checkpoint record, but I could understand why > someone might think that "start" is the location of the previous checkpoi= nt > record and "end" is the redo location of the new one. I think your > original idea of "lsn=3D%X/%X, redo lsn=3D%X/%X" could be a good alternat= ive. > > =D0=86n any case, this patch is small and otherwise looks reasonable to m= e, so I > am going to mark it as ready-for-committer. Thanks for your review. In summary, we have these options to choose checkpoint LSN and last REDO LSN: 1) "start=3D%X/%X, end=3D%X/%X" (ControlFile->checkPointCopy.redo, ControlFile->checkPoint) 2) "lsn=3D%X/%X, redo lsn=3D%X/%X" 3) "location=3D%X/%X, REDO location=3D%X/%X" -- similar to what pg_controldata and pg_control_checkpoint shows currently. 4) "location=3D%X/%X, REDO start location=3D%X/%X" I will leave that decision to the committer. Regards, Bharath Rupireddy.