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 1nDK5d-0008Py-09 for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Jan 2022 05:46:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nDK5b-0005cB-Qz for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Jan 2022 05:46:27 +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 1nDK5b-0005c2-IS for pgsql-hackers@lists.postgresql.org; Fri, 28 Jan 2022 05:46:27 +0000 Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nDK5Y-000809-Fv for pgsql-hackers@lists.postgresql.org; Fri, 28 Jan 2022 05:46:27 +0000 Received: by mail-pl1-x62e.google.com with SMTP id j16so4931740plx.4 for ; Thu, 27 Jan 2022 21:46:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=6X+fJlc/YAiZz0hGejNQ00LAS6egDEbA4RCju33Um8Q=; b=VW6sXbj3ZcVhSCkohbzItBtp2+o2Fsikep2C9XCcmear0feFZ/DeuJj4Wmx9+4Yv4W eXqPJrimMB/i8UsxkXzQYOLmHGTMUFE0XpQPtuDobjm+wtyH+JL5GK85xfjNnsKfBfU6 GWjO1lMQ78qDncVplu0wMuZj5fUqozOEm46fuDOGZrheo7n+psNrI5CYDuwRip2bMkLV sLzTBMdXq/5VTfC1UfBtpGkD5o8pGwJA/yI/pNRTB9Gu1InUc3zvKDqNC8lzAq9lLRQ3 s0dvgyBcvc+BJYfOy9meO/V9KNn/y9PQ4s37GfiZ8Nlrykpemyj4u7i1ciaYbaiSMKTb 9gJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=6X+fJlc/YAiZz0hGejNQ00LAS6egDEbA4RCju33Um8Q=; b=pkzL3KJ3ZFYg2nUTqB5CABCiI93YZ+z9Ax/xpM2MIMlbSOKwcEMB5gT8bX1s1B/oeu EISK94M99ARE2Y2DGg0obJ05fU3FDxpw9KS3Rkz/D+5tQ7jrbqvf7W8/lD7Qn+ibXt+c UjkyRxgFMok057w1lx4uoap6PyLVLVBK06Jcj45VKXKnPg3axgOecxbGbbZl4olput1I BVm4tgR+UnSs9NO9SEIaQ+gs/cmRwpNgMNMjif2AhBmLM7Ed+nctjhE5qXVyIn1W7elQ g8PIkNxqgcZBDcraMUYWPnoKKWdcf/GAKFmYJqonhg61yhTPk2HoOfbwdHy+rnqtBMA7 7ICA== X-Gm-Message-State: AOAM531yKbidJc84EUHv2Zby+CHNMteSRo08lV78JcHoO43OguvOvj1V PNzIttiLwIObElJqTWPWFAF9bHMIx1Y= X-Google-Smtp-Source: ABdhPJyYrKxb1p/O0dtR0BS4VlYSPeZnL2IXven9vuVAyAKYwh9ty4fLZIJGuD/gDzjtmRhseHJFhA== X-Received: by 2002:a17:902:da8b:: with SMTP id j11mr6872428plx.90.1643348782601; Thu, 27 Jan 2022 21:46:22 -0800 (PST) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id f20sm997210pgh.60.2022.01.27.21.46.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Jan 2022 21:46:22 -0800 (PST) Date: Thu, 27 Jan 2022 21:46:20 -0800 From: Nathan Bossart To: Bharath Rupireddy Cc: Kyotaro Horiguchi , "Bossart, Nathan" , Julien Rouhaud , Michael Paquier , PostgreSQL Hackers Subject: Re: Add checkpoint and redo LSN to LogCheckpointEnd log message Message-ID: <20220128054620.GA654866@nathanxps13> References: <20220120.120029.1092463916382268628.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 28, 2022 at 08:43:36AM +0530, Bharath Rupireddy wrote: > 2022-01-28 03:06:10.213 UTC [2409486] LOG: checkpoint starting: > immediate force wait > 2022-01-28 03:06:10.257 UTC [2409486] LOG: checkpoint complete: > start=0/14D9510, end=0/14D9548; wrote 4 buffers (0.0%); 0 WAL file(s) > added, 0 removed, 0 recycled; write=0.007 s, sync=0.008 s, total=0.044 > s; sync files=3, longest=0.005 s, average=0.003 s; distance=0 kB, > estimate=0 kB > > 2022-01-28 03:06:42.254 UTC [2409486] LOG: checkpoint starting: > immediate force wait > 2022-01-28 03:06:42.279 UTC [2409486] LOG: checkpoint complete: > start=0/14DBDB8, end=0/14DBDF0; wrote 2 buffers (0.0%); 0 WAL file(s) > added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.025 > s; sync files=2, longest=0.003 s, average=0.002 s; distance=10 kB, > estimate=10 kB I know I voted for "start=%X/%X, end=%X/%X," but looking at this again, 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 checkpoint record and "end" is the redo location of the new one. I think your original idea of "lsn=%X/%X, redo lsn=%X/%X" could be a good alternative. Іn any case, this patch is small and otherwise looks reasonable to me, so I am going to mark it as ready-for-committer. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com/