Re: BUG #16484: pg_regress fails with --outputdir parameter

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, r(dot)zharkov(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16484: pg_regress fails with --outputdir parameter
Date: 2020-06-09 05:55:06
Message-ID: 2192706.1591682106@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> And this leads me to the attached.

That will create the output directory even if indir doesn't exist, which
seems likely to lead to bogus directories hanging around in places where
we don't need them --- plus it seems rather ugly to drop this into the
middle of the sequence concerned with indir. So shouldn't the new code
be after the exit for indir not existing?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vianello Fabio 2020-06-09 05:59:04 RE: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events
Previous Message Michael Paquier 2020-06-09 05:33:56 Re: BUG #16484: pg_regress fails with --outputdir parameter