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 1nv1Bx-0000Zr-Dm for pgsql-hackers@arkaria.postgresql.org; Sat, 28 May 2022 18:29:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nv1Bw-0005yV-9u for pgsql-hackers@arkaria.postgresql.org; Sat, 28 May 2022 18:29:36 +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 1nv1Bv-0005yM-Vs for pgsql-hackers@lists.postgresql.org; Sat, 28 May 2022 18:29:35 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nv1Bt-0001n2-Qv for pgsql-hackers@postgresql.org; Sat, 28 May 2022 18:29:35 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1D408320089C; Sat, 28 May 2022 14:29:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 28 May 2022 14:29:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1653762570; x= 1653848970; bh=pfaz6nYbloZ0v17hgIbHvI3TneAhJYT6qu32HMy0ChM=; b=n vPmwJ7i6QivVfGtg8ac9VDtyC6L1mqIGYWorRESvAUiwwAJYJmsp+MHpd8QIQLfU keWKoCGa1yK2iF2azwrIb6t8KA9GHwwykSTBVMW1HgMOPjGY6PX8fx1vk3FvvSlE 3uu5OtGSLizAWKKe34HYKqrpjKSUDy459dw8tbyDzskHAoC+Z8rDJctd6oR0Mjt2 VJNqWcXM6N4yjUzsaqfSS9/JfHwflMVMvY43saPMw5xN8cWhc/t0Yt1DK+snR02E xdsrzBW04Ju0NzDnS1T+lSfNo9HnJSAtgIBg8dQncSCDp1GJ2T60R1hqz8EUqTWY 2H/M1bjKnt/J5ZaTksVRg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkedugdduvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 28 May 2022 14:29:28 -0400 (EDT) Message-ID: Date: Sat, 28 May 2022 20:29:27 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: pg_upgrade test writes to source directory Content-Language: en-US To: Michael Paquier Cc: Justin Pryzby , pgsql-hackers@postgresql.org, Andres Freund References: <20220526205218.GC19626@telsasoft.com> <50915523-5e3d-e1c7-9c38-d17263146e41@enterprisedb.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 28.05.22 10:56, Michael Paquier wrote: > On Fri, May 27, 2022 at 02:45:57PM +0200, Peter Eisentraut wrote: >> I think you can just chdir to ${PostgreSQL::Test::Utils::tmp_check}. > > Hmm. I think that I prefer your initial suggestion with TESTOUTDIR. > This sticks better in the long term, while making things consistent > with 010_tab_completion.pl, the only test that moves to TESTDIR while > running. So my vote would be to backpatch first the addition of > TESTOUTDIR, then fix the TAP test of pg_upgrade on HEAD to do the > same. I think it's a bit premature to talk about backpatching, since the patch in question hasn't been committed anywhere yet, and AFAICT hasn't even really been reviewed yet. If you want to go this direction, I suggest you extract the patch and present it here on its own merit. -- But then I might ask why such a broad change post beta when apparently a one-line change would also work.