Re: A failure in 031_recovery_conflict.pl on Debian/s390x - Mailing list pgsql-hackers

From Andres Freund
Subject Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Date
Msg-id 20230807230821.gylo74fox445hu24@awork3.anarazel.de
Whole thread Raw
In response to Re: A failure in 031_recovery_conflict.pl on Debian/s390x  (Christoph Berg <myon@debian.org>)
Responses Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Re: A failure in 031_recovery_conflict.pl on Debian/s390x
List pgsql-hackers
Hi,

On 2023-08-07 12:57:40 +0200, Christoph Berg wrote:
> Re: Thomas Munro
> > Thanks for testing!  Would you mind trying v8 from that thread?  V7
> > had a silly bug (I accidentally deleted a 'case' label while cleaning
> > some stuff up, resulting in the above error...)
> 
> v8 worked better. It succeeded a few times (at least 12, my screen
> scrollback didn't catch more) before erroring like this:

> [10:21:58.410](0.151s) ok 15 - startup deadlock: logfile contains terminated connection due to recovery conflict
> [10:21:58.463](0.053s) not ok 16 - startup deadlock: stats show conflict on standby
> [10:21:58.463](0.000s)
> [10:21:58.463](0.000s) #   Failed test 'startup deadlock: stats show conflict on standby'
> #   at t/031_recovery_conflict.pl line 332.
> [10:21:58.463](0.000s) #          got: '0'
> #     expected: '1'

Hm, that could just be a "harmless" race. Does it still happen if you apply
the attached patch in addition?

Greetings,

Andres Freund

Attachment

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Using defines for protocol characters
Next
From: Jeff Davis
Date:
Subject: Re: Faster "SET search_path"