Re: pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEMSET. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEMSET.
Date
Msg-id 20190828012439.GA1965@paquier.xyz
Whole thread Raw
In response to pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEM SET.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEM SET.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Mon, Aug 26, 2019 at 09:03:08PM +0000, Tom Lane wrote:
> Fix 007_sync_rep.pl to notice failures in ALTER SYSTEM SET.
>
> If a test case tried to set an invalid value of synchronous_standby_names,
> the test script didn't detect that, which seems like a bad idea.
> Noticed while testing a proposed patch that broke some of these
> test cases.

Just for the note.  I think that this needs a closer lookup and I am
afraid that there are more issues like this one.  For example, in
012_subtransactions.pl, pg_reload_conf() is called with
PostgresNode::psql without checking for an error which is a bad idea
after switching to synchonous replication.  Most of the transactions
done in this scrupt should also complain immediately on an error.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Set application_name per-test in isolation and ecpg tests.
Next
From: Michael Paquier
Date:
Subject: pgsql: Disable timeouts when running pg_rewind with online sourceclust