Re: Unstable tests for recovery conflict handling - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Unstable tests for recovery conflict handling
Date
Msg-id 20220428012634.xobo2f7ipaeblv6a@alap3.anarazel.de
Whole thread Raw
In response to Re: Unstable tests for recovery conflict handling  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
Hi,

On 2022-04-27 10:11:53 -0700, Mark Dilger wrote:
> 
> 
> > On Apr 27, 2022, at 9:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > 
> > [ starting a new thread cuz the shared-stats one is way too long ]
> > 
> > Andres Freund <andres@anarazel.de> writes:
> >> Add minimal tests for recovery conflict handling.
> > 
> > It's been kind of hidden by other buildfarm noise, but
> > 031_recovery_conflict.pl is not as stable as it should be [1][2][3][4].
> > 
> > Three of those failures look like
> 
> Interesting,
> 
> I have been getting failures on REL_14_STABLE:
> 
> t/012_subtransactions.pl ............. 11/12                                                            
> #   Failed test 'Rollback of PGPROC_MAX_CACHED_SUBXIDS+ prepared transaction on promoted standby'
> #   at t/012_subtransactions.pl line 211.
> #          got: '3'
> #     expected: '0'
> t/012_subtransactions.pl ............. 12/12 # Looks like you failed 1 test of 12.
> t/012_subtransactions.pl ............. Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/12 subtests 
> 
> And the logs, tmp_check/log/regress_log_012_subtransactions, showing:

I'm a bit confused - what's the relation of that failure to this thread / the
tests / this commit?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: "shiy.fnst@fujitsu.com"
Date:
Subject: RE: Data is copied twice when specifying both child and parent table in publication
Next
From: Andres Freund
Date:
Subject: Re: Unstable tests for recovery conflict handling