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 1nBtSN-00036U-7E for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 07:08:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nBtSL-0005yg-IY for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 07:08:01 +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 1nBtSL-0005yW-5J for pgsql-hackers@lists.postgresql.org; Mon, 24 Jan 2022 07:08:01 +0000 Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nBtSH-0005Cl-87 for pgsql-hackers@postgresql.org; Mon, 24 Jan 2022 07:07:59 +0000 Received: by mail-io1-xd2d.google.com with SMTP id n17so2456423iod.4 for ; Sun, 23 Jan 2022 23:07:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hYmqe4ZVY7R7JjFCr/z3JuR69lqrUCoEbdy545rbyLY=; b=sp2ccYLuKyn4+fA5bRz5iOktOToZZWfHim2RZn2b6h5rENwkByW7LBTlx/sRUrbbLn iDJ0QIECtTj0WNbcvEe4i966F+GF7JQWFKP9yhwVpHeDRW0QYUHRxsTmlChKDCMCZPzq xY6xnd5pefQgk6F2UslfB1pBU2SXGRdFMO+kzy9c6mIXDV5DwFuva9onTa0xaVdSlWmW Yf39O7ihRedfAn+9x5+8/VNHhVvJ1uL6TZ8Ey6kMVgRfYraVwO8FjvbXvMJPAQNEGovm Y9yYH3kpI3UUG8JVNd/DtEfSExKPrbXY6k3PTtyQGJ+wbkVxQKrXDZ3uHfy4Du2mSot+ pIsw== 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:in-reply-to:user-agent; bh=hYmqe4ZVY7R7JjFCr/z3JuR69lqrUCoEbdy545rbyLY=; b=T+djNGtx3OxdBTShmlJ4IslpidtzXqJjx4JEubcXD8WFWLyCdViVpX2/VSPv+UCy0M NdKrIFeikOZKxdUP7oI2vBLvRqRdVQnPCgLMY0F/lEdvTqAWOu6rK1Y/1ya+0+u45unh TRaXCtGvAt0+SjWghPxmPdAeZ3p1IMYHCuf2sq1aTmbgsXFgJ4AtXWQ61e1EJ3AwpSQy sZMc02BGUKNXc19yzngrEA3Dqf/MvhElneeXA9inemtye5uYEn3U3D1fr2jLY8fYSoVc vYJyIKTxK//xNnZiittSFGalViOJXjk6GH8yKZ6WeBYEYkI7guuVGN+DuEGoA5bD/Hr0 +Z5Q== X-Gm-Message-State: AOAM533h1ZM8DAjkU0LDJShMQwXCQQ0Qj8PZQ67CMy6j/ObHKKN2wguC cgrrU4Qd8ejSbHIg2EfClKFlMg== X-Google-Smtp-Source: ABdhPJxYdi8iByuKK2AORMMXjnd2Ki6jyBx23lxyi9s3MKj6Zi6MoyVsd0BXOwRWnn9vl5NDVhSbRA== X-Received: by 2002:a05:6638:a8d:: with SMTP id 13mr5989929jas.68.1643008076060; Sun, 23 Jan 2022 23:07:56 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id m4sm6880746iln.48.2022.01.23.23.07.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Jan 2022 23:07:55 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 683D6800783; Mon, 24 Jan 2022 01:07:54 -0600 (CST) Date: Mon, 24 Jan 2022 01:07:54 -0600 From: Justin Pryzby To: Michael Paquier Cc: pgsql-hackers@postgresql.org Subject: Re: typos Message-ID: <20220124070754.GT23027@telsasoft.com> References: <20220124030001.GQ23027@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jan 24, 2022 at 04:01:47PM +0900, Michael Paquier wrote: > On Sun, Jan 23, 2022 at 09:00:01PM -0600, Justin Pryzby wrote: > > Feel free to ignore this for now and revisit in April... > > I don't mind fixing that now. That means less to do later. Thanks. > > @Michael: I'm not sure what this is trying to say. > > 1e9475694b0ae2cf1204d01d2ef6ad86f3c7cac8 > > + First, scan the directory where the WAL segment files are written and > > + find the newest completed segment file, using as starting point the > > + beginning of the next WAL segment file. This is calculated independently > > + on the compression method used to compress each segment. > > > > I suppose it should say independently *of* the compression method, but then I > > still don't know what it means. I checked FindStreamingStart(). > > It that doesn't look like it's "calculated independently" - actually, it takes > > the compression method into account and explicitly handles each compression > > method. > > This means that we are able to calculate the starting LSN even if the > segments stored use different compression methods or are > uncompressed. Would you reword that differently? Or perhaps removing > the last sentence of this paragraph would be simpler in the long run? different from what? From each other ? Maybe I would have written: | This is calculated separately for each segment, which may each use | different compression methods. But probably I would just remove it. -- Justin