Re: Adding a TAP test checking data consistency on standby withminRecoveryPoint - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Adding a TAP test checking data consistency on standby withminRecoveryPoint
Date
Msg-id 20190416064512.GJ2673@paquier.xyz
Whole thread Raw
In response to Re: Adding a TAP test checking data consistency on standby withminRecoveryPoint  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint
List pgsql-hackers
On Sun, Mar 24, 2019 at 09:47:58PM +0900, Michael Paquier wrote:
> The failure is a bit weird, as I would expect all those three actions
> to be sequential.  piculet is the only failure happening on the
> buildfarm and it uses --disable-atomics, so I am wondering if that is
> related and if 0dfe3d0 is part of that.  With a primary/standby set,
> it could be possible to test that scenario pretty easily.  I'll give
> it a shot.

The buildfarm has just failed with a similar failure, for another
test aka 009_twophase.pl:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dragonet&dt=2019-04-16%2006%3A14%3A01

I think that we have race conditions with checkpointing and shutdown
on HEAD.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: REINDEX CONCURRENTLY 2.0
Next
From: Magnus Hagander
Date:
Subject: Re: Commit message / hash in commitfest page.