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 1nD6NR-0001xJ-L1 for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jan 2022 15:07:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nD6NP-00036P-6U for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jan 2022 15:07:55 +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 1nD6NO-00036E-Sd for pgsql-hackers@lists.postgresql.org; Thu, 27 Jan 2022 15:07:54 +0000 Received: from mail-pj1-x1034.google.com ([2607:f8b0:4864:20::1034]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nD6NJ-0005sE-TV for pgsql-hackers@lists.postgresql.org; Thu, 27 Jan 2022 15:07:54 +0000 Received: by mail-pj1-x1034.google.com with SMTP id h12so3232286pjq.3 for ; Thu, 27 Jan 2022 07:07:49 -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; bh=auHCQCaCdsIX0qH/vB9GB5aiXsCgZJVfbCh29kz+fUM=; b=VisH9KntWCm6WEWtbwmW1KcP4pMDNPqkCItL3XQlx6pDMuH2tnZcBIUU77SnDC7y8P zTg8SzWytyRn51pHyMH0VK8vts3prtP30uCg/lFQ3jOvJGebxbtify7yXkhY/fU3zQzt oZDcUFNhDoAXry3sHgH3eOwsW3MDoa/yGAz9I/OpXAyD0Pk8An6jMDuZknnoSjEyb3+l iRWz+eaNxMgYvioxv8KIeEjz8wpNidZto5PKTiZFnDCAiO9uG5+XdrMQEkPoJ+0Mcr2V mSA6aED0JEP5qg7n909hY6yM3w79DGQ38mERZZJ4L/1wwmlBNJemKmuH3X+X6SZk4P/7 /MVQ== 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; bh=auHCQCaCdsIX0qH/vB9GB5aiXsCgZJVfbCh29kz+fUM=; b=QbIWTcOSSJB9SgEB/vrkD8WUZqmciIeu06wU0U4wxRfW1jI/MEgmprHUFJBqfaDJo7 eCLpKjhwTfe/6J2KSnchwT1ta9+XDOA0GJCVOhMaLc8+ZbtKMgs+hUFll+oGRCHE3Kpf O7raiGaaV57mPArBxJF3vCPQ2L5jo6fnRsYc1JxVZG/c15omDXi0pdWS6NuBDQT+Hf67 mfNEPbr3v2oziu0anWVd+Y+CvXIGNIPRwQJh9s3pWHCBW/J8JaRkNgHUiZdowlasdJdK J/cA2TFnik9L8uIrk+TbWZRwzCo76tcWUtrPw7UkV7RUzxYOwssdJpiRmeOOfj1NVqN1 0FLA== X-Gm-Message-State: AOAM532xkjAAmv0T+vuo2dQDztSktRjhFWKe3VKofd2izkUuS1dwSyFF ZvrYuM2qnRFAiqQfa7yd4lqfdxlKThaHi5EFoXM= X-Google-Smtp-Source: ABdhPJz1Lm8i8FikWkA7pCe5GZ+xSJJ2idZwDUffKr85v/rkx9SbZ2s15S4fpnmOx61K3a5rDOWNrwH3y0edBxUBRWc= X-Received: by 2002:a17:902:b094:: with SMTP id p20mr3705388plr.8.1643296067925; Thu, 27 Jan 2022 07:07:47 -0800 (PST) MIME-Version: 1.0 References: <20211224.145134.1164706994861031206.horikyota.ntt@gmail.com> In-Reply-To: From: Bharath Rupireddy Date: Thu, 27 Jan 2022 20:37:37 +0530 Message-ID: Subject: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message To: "Bossart, Nathan" Cc: Julien Rouhaud , Michael Paquier , Kyotaro Horiguchi , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jan 20, 2022 at 6:06 AM Bossart, Nathan wrote: > > On 1/3/22, 5:52 PM, "Kyotaro Horiguchi" wrote: > > 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]".. > > My first instinct was that this should stay aligned with > pg_controldata, but that would mean using "location=%X/%X, REDO > location=%X/%X," which doesn't seem terribly descriptive. IIUC the > "checkpoint location" is the LSN of the WAL record for the checkpoint, > and the "checkpoint's REDO location" is the LSN where checkpoint > creation began (i.e., what you must retain for crash recovery). My > vote is for "start=%X/%X, end=%X/%X." I'm still not clear how the REDO location can be treated as a start LSN? Can someone throw some light one what this checkpoint's REDO location is? Regards, Bharath Rupireddy.