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 1ocswU-0006a3-Jt for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Sep 2022 18:34:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ocswT-0003t9-EA for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Sep 2022 18:34:57 +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 1ocswT-0003rs-4Z for pgsql-hackers@lists.postgresql.org; Mon, 26 Sep 2022 18:34:57 +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 1ocswO-00027q-K9; Mon, 26 Sep 2022 18:34:56 +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 28QIYkBL3492534; Mon, 26 Sep 2022 14:34:46 -0400 From: Tom Lane To: Justin Pryzby cc: "Jonathan S. Katz" , Alvaro Herrera , Nathan Bossart , Bruce Momjian , pgsql-hackers@postgresql.org, David Rowley Subject: Re: First draft of the PG 15 release notes In-reply-to: <20220925215009.GC21938@telsasoft.com> References: <20220913111333.c56vyzgipzzyzimu@alvherre.pgsql> <2121704.1663946744@sss.pgh.pa.us> <24c8bb66-73ab-199b-b99a-21d8d7e0b273@postgresql.org> <2134470.1663954387@sss.pgh.pa.us> <20220925215009.GC21938@telsasoft.com> Comments: In-reply-to Justin Pryzby message dated "Sun, 25 Sep 2022 16:50:09 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3492532.1664217286.1@sss.pgh.pa.us> Date: Mon, 26 Sep 2022 14:34:46 -0400 Message-ID: <3492533.1664217286@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Justin Pryzby writes: > On Fri, Sep 23, 2022 at 01:33:07PM -0400, Tom Lane wrote: > + Previously such files were left in the current directory, > + requiring manual cleanup. It's still necessary to remove them > + manually afterwards, but now one can just remove that whole > + subdirectory. > If pg_upgrade succeeds, then it removes the dir itself (so it's not > "necessary"). Ah, I'd only ever paid attention to failure cases, so I didn't realize that :-(. Text adjusted: Previously such files were left in the current directory, requiring manual cleanup. Now they are automatically removed on successful completion of pg_upgrade. I took most of your other suggestions, too. Thanks! regards, tom lane