| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_regress cleans up tablespace twice. |
| Date: | 2020-02-19 21:06:33 |
| Message-ID: | 9977.1582146393@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> writes:
> But in the first place it comes from [1] and the comment says:
>> * XXX it would be better if pg_regress.c had nothing at all to do with
>> * testtablespace, and this were handled by a .BAT file or similar on
>> * Windows. See pgsql-hackers discussion of 2008-01-18.
> Is there any reason not to do that in vcregress.pl? I think the
> commands other than 'check' don't needs this.
I think the existing coding dates from before we had a Perl driver for
this, or else we had it but there were other less-functional ways to
replace "make check" on Windows. +1 for taking the code out of
pg_regress.c --- but I'm not in a position to say whether the other
part of your patch is sufficient.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-02-19 21:14:02 | Re: Yet another fast GiST build |
| Previous Message | Tom Lane | 2020-02-19 20:55:38 | Re: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare() |