Re: pg_upgrade test writes to source directory - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade test writes to source directory
Date
Msg-id b68a2c98-8690-c057-c9e1-79bc6db608a0@enterprisedb.com
Whole thread Raw
In response to Re: pg_upgrade test writes to source directory  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_upgrade test writes to source directory
List pgsql-hackers
On 25.05.22 09:25, Michael Paquier wrote:
>> It looks like an addition of
>>
>>      chdir $ENV{TESTOUTDIR};
>>
>> could fix it.  Please check the patch.
> I think that you mean TESTDIR, and not TESTOUTDIR?

I chose TESTOUTDIR because it corresponds to the tmp_check directory, so 
that the output files of the pg_upgrade run are removed when the test 
artifacts are cleaned up.  When using TESTDIR, the pg_upgrade output 
files end up in the build directory, which is less bad than the source 
directory, but still not ideal.



pgsql-hackers by date:

Previous
From: "Imseih (AWS), Sami"
Date:
Subject: Re: Add index scan progress to pg_stat_progress_vacuum
Next
From: jian he
Date:
Subject: ICU_LOCALE set database default icu collation but not working as intended.