Re: Race-like failure in recovery/t/009_twophase.pl

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Race-like failure in recovery/t/009_twophase.pl
Date: 2017-07-03 01:15:15
Message-ID: CAB7nPqSOFT7Tg8Qk+tkzXZezWPbcc4THr924mHb1+PMN55RbxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(catching up test threads)

On Mon, Jul 3, 2017 at 7:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm now inclined to think that the correct fix is to ensure that we
> run synchronous rep in both directions, rather than to insert delays
> to substitute for that. Just setting synchronous_standby_names for
> node paris at the top of the script doesn't work, because there's
> at least one place where the script intentionally issues commands
> to paris while london is stopped.

I bet that using syncrep in both directions will likely avoid
inconsistencies in the future if the test suite is extended on way or
another.

> But we could turn off sync rep for that step, perhaps.

Yeah, by using synchronous_commit = off.

> Anyone have a different view of what to fix here?

No, this sounds like a good plan. What do you think about the attached?
--
Michael

Attachment Content-Type Size
2pc-test-fix.patch application/octet-stream 2.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-07-03 01:23:59 Re: Race-like failure in recovery/t/009_twophase.pl
Previous Message Michael Paquier 2017-07-03 00:46:21 Re: PostgresNode::poll_query_until hacking