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 1o9UD4-0007WN-4a for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Jul 2022 16:18:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o9UD3-0004aY-1J for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Jul 2022 16:18:33 +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 1o9UD2-0004ZV-My for pgsql-hackers@lists.postgresql.org; Thu, 07 Jul 2022 16:18:32 +0000 Received: from mail-pf1-x433.google.com ([2607:f8b0:4864:20::433]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o9UD0-00069L-AO for pgsql-hackers@postgresql.org; Thu, 07 Jul 2022 16:18:31 +0000 Received: by mail-pf1-x433.google.com with SMTP id 70so5272993pfx.1 for ; Thu, 07 Jul 2022 09:18:30 -0700 (PDT) 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:in-reply-to; bh=UpMasas7JDIJ+Ku/V92DDSE+DLLwHZRl3DtAoNfEWdg=; b=kvGaJsLSaLRrjxZ0txra/R91xtdvyIMfapE4IjjCzPo5A8iDGiMIaLRqqs4FzSXs/5 rqBHeCctSfyWDu7mUoM6DrT4NvsoBB0bkL7rRxZ5EMF5TWoeQrCdhIz4vVSkRPqIaRUB rmk9bdiL6Fm/MxqU9ZIDoQosEVHaRHZEMffxwdQyumzOL6jS+8GGWRUkeosaeQvyz+wI ah5hsdFAwiKTrV1zAmKBxcDxt5MGmYFP22urinibeHUotH7yTKCqGQ2+ZLHUjoreD0WW HCLv1dMQStpGqIwMGw3hrNupjEMF2t90uLspwX+h1xWzyLSO+79zeE5uKy8neDaaDp5D kJzA== 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; bh=UpMasas7JDIJ+Ku/V92DDSE+DLLwHZRl3DtAoNfEWdg=; b=w8a4GWqR2gnTYQmmugyrLRk7rKSuZ4JzK3kVGVGUtq+nIaXQpkzSfP+GUCTB9dU2IL KloxtqRojGtd8A10dphOTk6ND1PjdhI54ShrKteDNLRYQMSIE7Axi6vsjg8Jzl2TJr5h rFRZXfN+GlhIsU6W8vG9aJFUNczw8nXcBASVpW1MZBL9aQuT9kdi+DWKkQx/upni473B 6EbchIsv+5vUES/PEcxAXfMWudc0/gDp7hXV/ED4tUhcKulPcNPP5eaB7TUqWAgWZM5I gSIhzZavf2MOBlntjCxQ3fBDqbbIGg3J1oicx5w97ZqNeYaNN1mPDEQgpXqWce2+PY7u Gwig== X-Gm-Message-State: AJIora+X3Qfw0VO7OrW699wOXrcTeVRXVK1FbVmiVTQnKTvNj6Ag2gQI 742BG4AvvseD1OgBon2rDHs= X-Google-Smtp-Source: AGRyM1ukRWSYlriiZniTg5A8xvF2U88k0AvvPhHmUqEGjU29Huwpx5tKhSxxNAikpUgC7fTM6Gql3w== X-Received: by 2002:a62:a50e:0:b0:528:cc50:82db with SMTP id v14-20020a62a50e000000b00528cc5082dbmr3642953pfm.43.1657210709185; Thu, 07 Jul 2022 09:18:29 -0700 (PDT) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id ij7-20020a170902ab4700b0016bd8a76f67sm10684929plb.67.2022.07.07.09.18.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Jul 2022 09:18:28 -0700 (PDT) Date: Thu, 7 Jul 2022 09:18:25 -0700 From: Nathan Bossart To: David Steele Cc: Robert Haas , Fujii Masao , Kyotaro Horiguchi , "pgsql-hackers@postgresql.org" Subject: Re: remove more archiving overhead Message-ID: <20220707161825.GA2205004@nathanxps13> References: <20220222011948.GA3850532@nathanxps13> <20220222173711.GA3852671@nathanxps13> <20220222195229.GA42988@nathanxps13> <20220224.141349.1809640551882183816.horikyota.ntt@gmail.com> <20220224175553.GA660690@nathanxps13> <20220407222327.GA1363808@nathanxps13> <768e6cb3-256d-9c0b-1797-62420ffca7ae@oss.nttdata.com> <17147b74-5465-9a7a-ae27-305d1200482c@pgmasters.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17147b74-5465-9a7a-ae27-305d1200482c@pgmasters.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jul 07, 2022 at 10:46:23AM -0400, David Steele wrote: > On 7/7/22 10:37, Robert Haas wrote: >> On Thu, Jul 7, 2022 at 10:03 AM Fujii Masao wrote: >> > Thanks for updating the patch. It looks good to me. >> > Barring any objection, I'm thinking to commit it. >> >> I don't object, but I just started to wonder whether the need to >> handle re-archiving of the same file cleanly is as well-documented as >> it ought to be. > > +1, but I don't think that needs to stand in the way of this patch, which > looks sensible to me as-is. I think that's what you meant, but just wanted > to be sure. Yeah, this seems like something that should be documented. I can pick this up. I believe this is an existing problem, but this patch could make it more likely. > There are plenty of ways that already-archived WAL might get archived again > and this is just one of them. What are some of the others? I was aware of the case that was fixed in ff9f111, where we might try to re-archive a file with different contents, but I'm curious what other ways you've seen this happen. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com