Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc. - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.
Date
Msg-id CAMsr+YHwktJGG9ArempaoNytzt_f0+Ms3DLwJBwR4DqUktc8Ag@mail.gmail.com
Whole thread Raw
In response to Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 1 March 2016 at 21:05, Craig Ringer <craig@2ndquadrant.com> wrote:
On 1 March 2016 at 20:45, Michael Paquier <michael.paquier@gmail.com> wrote:
On Tue, Mar 1, 2016 at 5:13 PM, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> 0001-Change-behavior-...
>
>   Changes of PostmasterNode.pm and TestLib.pm to add some
>   features and change a behavior.

+   # Preserve temporary directory for this test if failure
+   $File::Temp::KEEP_ALL = 1 unless Test::More->builder->is_passing;
+1. Having the data folders being removed even in case of a failure is
really annoying.

I agree on all points re your review. Keeping tempdirs is really needed, the tempdir name change is good, the  the rest I'm not keen on.

I've addressed the need to get stderr from psql in a patch I'll submit separately, which provides a thinner wrapper around IPC::Run for more complex needs, then uses that for the existing 'psql' function. It also provides a 'psql_check' that dies on error.

I'll incorporate the wanted changes into that patch.

OK, done.


Michael, I'd value your thoughts on the patches. I think the psql one is important, I found the existing 'psql' function too limiting and I think defaulting to ignoring errors is sub-optimal.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: TAP / recovery-test fs-level backups, psql enhancements etc
Next
From: Craig Ringer
Date:
Subject: Re: Timeline following for logical slots