From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: pg_upgrade test writes to source directory |
Date: | 2022-05-28 18:29:27 |
Message-ID: | defe6fe7-5824-5d87-b14f-0faee07e0b04@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-05-28 19:14:42 | Re: [RFC] building postgres with meson |
Previous Message | Peter Eisentraut | 2022-05-28 18:25:20 | Re: CREATE COLLATION must be specified |