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

Commit 27e97d0

Browse files
committed
Revert "Fix timing issue in deadlock recovery conflict test."
This reverts commit 8a3a8d9.
1 parent 8a3a8d9 commit 27e97d0

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

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

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -231,14 +231,6 @@
231231
$sect = "startup deadlock";
232232
$expected_conflicts++;
233233

234-
# Want to test recovery deadlock conflicts, not buffer pin conflicts. Without
235-
# changing max_standby_streaming_delay it'd be timing dependent what we hit
236-
# first
237-
$node_standby->adjust_conf('postgresql.conf', 'max_standby_streaming_delay',
238-
"${PostgreSQL::Test::Utils::timeout_default}s");
239-
$node_standby->restart();
240-
reconnect_and_clear();
241-
242234
# Generate a few dead rows, to later be cleaned up by vacuum. Then acquire a
243235
# lock on another relation in a prepared xact, so it's held continuously by
244236
# the startup process. The standby psql will block acquiring that lock while
@@ -294,9 +286,6 @@
294286

295287
# clean up for next tests
296288
$node_primary->safe_psql($test_db, qq[ROLLBACK PREPARED 'lock';]);
297-
$node_standby->adjust_conf('postgresql.conf', 'max_standby_streaming_delay', '50ms');
298-
$node_standby->restart();
299-
reconnect_and_clear();
300289

301290

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

0 commit comments

Comments
 (0)