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

From Tom Lane
Subject Re: pg_upgrade test writes to source directory
Date
Msg-id 11298.1660231599@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade test writes to source directory  (Andres Freund <andres@anarazel.de>)
Responses Re: pg_upgrade test writes to source directory
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2022-06-01 10:55:28 -0400, Tom Lane wrote:
>> [...] I'm definitely not happy with the proposed changes to
>> 010_tab_completion.pl.  My recollection is that those tests
>> were intentionally written to test tab completion involving a
>> directory name, but this change just loses that aspect entirely.

> How about creating a dedicated directory for the created files, to maintain
> that? My goal of being able to redirect the test output elsewhere can be
> achieved with just a hunk like this:

Sure, there's no need for these files to be in the exact same place that
the output is collected.  I just want to keep their same relationship
to the test's CWD.

> Of course it'd need a comment adjustment etc. It's a bit ugly to use a
> otherwise empty tmp_check/ directory just to reduce the diff size, but it's
> also not too bad.

Given that it's no longer going to be the same tmp_check dir used
elsewhere, maybe we could s/tmp_check/tab_comp_dir/g or something
like that?  That'd add some clarity I think.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_upgrade test writes to source directory
Next
From: Tom Lane
Date:
Subject: Re: tests and meson - test names and file locations