Re: pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEM SET.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix 007_sync_rep.pl to notice failures in ALTER SYSTEM SET.
Date: 2019-08-28 01:24:39
Message-ID: 20190828012439.GA1965@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2019-08-28 02:50:25 pgsql: Disable timeouts when running pg_rewind with online source clust
Previous Message Tom Lane 2019-08-27 23:49:29 pgsql: Set application_name per-test in isolation and ecpg tests.