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 1oblJd-00069R-FU for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2022 16:14:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oblJc-0008CZ-Cp for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2022 16:14:12 +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 1oblJc-0008C9-17 for pgsql-hackers@lists.postgresql.org; Fri, 23 Sep 2022 16:14:12 +0000 Received: from mail-pl1-x630.google.com ([2607:f8b0:4864:20::630]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oblJZ-0006Zw-86 for pgsql-hackers@postgresql.org; Fri, 23 Sep 2022 16:14:11 +0000 Received: by mail-pl1-x630.google.com with SMTP id x1so617034plv.5 for ; Fri, 23 Sep 2022 09:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=MN3c8DSgOtxpX0wZJuu6ZecUY3rK5cEeGO+SIRiKsT8=; b=DkX7+R9fxl7CWOKgLBTVwTqqv04SglMa4TCzXbh+6YOQBOk0Z46J75V43pKk4P2XJX wQ1u5q9YNaqxJuuFDdwy6kjlknHOczsIE6WTlk7RFUnYPf948euwRICXs3MU+/QfKniu 5MYFVIfyM7FvzLftEow3Jv8xhkj3A6JqS9iBnl4EVn1djNIgARr4+WgQKn1Vn+JurPko Fx9WY+u6YcvTHS1GFD24CROwbbPEluxrMjdzO9bgUx8FTXW+U1+5yAgoIlDxUHJbRBMH MlHzf5bzTp6YwOdbvuANYyYilaZQYtR+4FX5cvrejKxvXB6G319Iqz/Gw+5SUhoau64x zXDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=MN3c8DSgOtxpX0wZJuu6ZecUY3rK5cEeGO+SIRiKsT8=; b=eymnTCa8iGazNWLL+B/I192TmE0pggl8ljD7HTk8PV56p/6GZY9p7DyphwDGadR+ZK f6+vL/98Od0Y+4LFB2Ca9Rau3SdHO+w9JAaLP5LESuiFCVKhL2pw/pr4EQn8AfJzpq6t Dyyb50NiNv5z9cyq5zTvMtqJWOcPnR645OOPS7fWfSkm2hD9b6YBGhDPEoHReX+60Ffi SmgKXJbwULSbvxy1qGUDZBHc/bxC3L6bktg0y21TUvIvpiRyNihDW1cY+PuT6wsMkcJp gUMTjj4c9Ar8l2ositGI1iMl6VZ6zh7MI35aqncjOAH05MTe7rKBrw1iRc1OEut5SMfF aZ+A== X-Gm-Message-State: ACrzQf08YK1p0Jjzp2bsi4aETZVa5QyK/rvS1iLfQZ7ln/E7W/MpjLk+ SSvmXDS7qrb39PLGrILbT80= X-Google-Smtp-Source: AMsMyM4NixuwvDipxLjwS6f2PaLa3pI2/jHmtGGV18W3g3dMSzFiqIfvc+KdPCdUGhMrdnKRvKrn+g== X-Received: by 2002:a17:90b:164a:b0:202:5f0f:290e with SMTP id il10-20020a17090b164a00b002025f0f290emr22023417pjb.27.1663949646890; Fri, 23 Sep 2022 09:14:06 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id c190-20020a624ec7000000b00540f3ac5fb8sm6619146pfb.69.2022.09.23.09.14.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Sep 2022 09:14:06 -0700 (PDT) Date: Fri, 23 Sep 2022 09:14:02 -0700 From: Nathan Bossart To: Peter Eisentraut Cc: Tom Lane , Benoit =?iso-8859-1?Q?Lobr=E9au?= , Alvaro Herrera , Robert Haas , "Bossart, Nathan" , David Steele , Fujii Masao , "pgsql-hackers@postgresql.org" , Michael Paquier , Magnus Hagander , Stephen Frost Subject: Re: archive modules Message-ID: <20220923161402.GA736566@nathanxps13> References: <613541.1662842656@sss.pgh.pa.us> <20220910211046.GA2651323@nathanxps13> <9ee5d180-2c32-a1ca-d3d7-63a723f68d9a@enterprisedb.com> <20220914200305.GA2984249@nathanxps13> <37857474-5caa-ccb3-92a3-150ddfe851ab@enterprisedb.com> <2884265.1663188443@sss.pgh.pa.us> <20220914211746.GA2986134@nathanxps13> <2910705.1663193529@sss.pgh.pa.us> <20220914222736.GA3042279@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Sep 23, 2022 at 05:58:42AM -0400, Peter Eisentraut wrote: > On 15.09.22 00:27, Nathan Bossart wrote: >> Both archive_command and archive_library are PGC_SIGHUP, so IIUC that >> wouldn't be sufficient. I attached a quick sketch that seems to provide >> the desired behavior. It's nowhere near committable yet, but it >> demonstrates what I'm thinking. > > What is the effect of issuing a warning like in this patch? Would it just > not archive anything until the configuration is fixed? I'm not sure what > behavior you are going for; it's a bit hard to imagine from just reading the > patch. Yes, it will halt archiving and emit a WARNING, just like what happens on released versions when you leave archive_command empty. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com