Re: The real reason why TAP testing isn't ready for prime time - Mailing list pgsql-hackers

From Tom Lane
Subject Re: The real reason why TAP testing isn't ready for prime time
Date
Msg-id 5054.1434725109@sss.pgh.pa.us
Whole thread Raw
In response to Re: The real reason why TAP testing isn't ready for prime time  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: The real reason why TAP testing isn't ready for prime time  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> Attached is a patch fixing those problems and improving the log
> facility as it really helped me out with those issues. The simplest
> fix would be to include the -w switch missing in the tests of
> pg_rewind and pg_ctl though.

I agree with adding the -w switch and will go do that.  As far as the
rest of this patch goes, it seems like it could be made less invasive
if the logs got dumped into a subdirectory of tmp_check rather than
adding another top-level directory that has to be cleaned?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Time to get rid of PQnoPasswordSupplied?
Next
From: Andres Freund
Date:
Subject: pg_receivexlog --create-slot-if-not-exists