Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4e39957

Browse files
committed
Temporarily skip recovery deadlock test in back branches.
The recovery deadlock test has a timing issue that was fixed in 5136967 in HEAD. Unfortunately the same fix doesn't quite work in the back branches: 1) adjust_conf() doesn't exist, which is easy enough to work around 2) a restart cleares the recovery conflict stats < 15. These issues can be worked around, but given the upcoming set of minor releases, skip the problematic test for now. The buildfarm doesn't show failures in other parts of 031_recovery_conflict.pl. Discussion: https://postgr.es/m/20220506155827.dfnaheq6ufylwrqf@alap3.anarazel.de Backpatch: 10-14
1 parent 6ab90d2 commit 4e39957

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/test/recovery/t/031_recovery_conflict.pl

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -228,6 +228,10 @@
228228

229229

230230
## RECOVERY CONFLICT 5: Deadlock
231+
SKIP:
232+
{
233+
skip "disabled until after minor releases, due to instability";
234+
231235
$sect = "startup deadlock";
232236
$expected_conflicts++;
233237

@@ -286,6 +290,7 @@
286290

287291
# clean up for next tests
288292
$node_primary->safe_psql($test_db, qq[ROLLBACK PREPARED 'lock';]);
293+
}
289294

290295

291296
# Check that expected number of conflicts show in pg_stat_database. Needs to

0 commit comments

Comments
 (0)