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 1nYFpQ-0002DD-Fl for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Mar 2022 23:28:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nYFpP-0001nc-Ax for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Mar 2022 23:28:15 +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 1nYFpP-0001nS-1d for pgsql-hackers@lists.postgresql.org; Sat, 26 Mar 2022 23:28:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nYFpN-0005E1-2D for pgsql-hackers@lists.postgresql.org; Sat, 26 Mar 2022 23:28:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22QNS7QP182768; Sat, 26 Mar 2022 19:28:07 -0400 From: Tom Lane To: Thomas Munro cc: Justin Pryzby , Andres Freund , Robert Haas , PostgreSQL Hackers , Magnus Hagander Subject: Re: pgsql: Add 'basebackup_to_shell' contrib module. In-reply-to: References: <20220315190428.2xf6klawmaq4nuyy@alap3.anarazel.de> <626827E9-4A50-493D-A8EE-EB3C238BB47F@anarazel.de> <20220325212707.fkevorahowgur5ux@alap3.anarazel.de> <20220326031353.GG28503@telsasoft.com> Comments: In-reply-to Thomas Munro message dated "Sun, 27 Mar 2022 12:12:07 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <182766.1648337287.1@sss.pgh.pa.us> Date: Sat, 26 Mar 2022 19:28:07 -0400 Message-ID: <182767.1648337287@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Sat, Mar 26, 2022 at 4:14 PM Justin Pryzby wrote: >> I see it here (and in cfbot), although I'm not sure how you created a new >> patch for the active CF, and not for the next CF. > Anyone who has ever been a CF manager has this power, it seems. I did > it myself once, by accident, and got told off by the active CF > manager. I'm not sure what the policy is for that. I have done it myself, although I've never been a CF manager, so maybe it was granted to all committers? regards, tom lane