From 6e98a46bdea0b4ce5a7e103d08cb9b804d2afea0 Mon Sep 17 00:00:00 2001 From: Hayato Kuroda Date: Fri, 7 Aug 2026 18:06:28 +0900 Subject: [PATCH] Stablize 038_walsnd_shutdown_timeout --- src/test/subscription/t/038_walsnd_shutdown_timeout.pl | 1 + 1 file changed, 1 insertion(+) diff --git a/src/test/subscription/t/038_walsnd_shutdown_timeout.pl b/src/test/subscription/t/038_walsnd_shutdown_timeout.pl index f4ed5d97852..fe9abd38239 100644 --- a/src/test/subscription/t/038_walsnd_shutdown_timeout.pl +++ b/src/test/subscription/t/038_walsnd_shutdown_timeout.pl @@ -46,6 +46,7 @@ $node_subscriber->wait_for_subscription_sync($node_publisher, 'test_sub'); # Start a background session on the subscriber to run a transaction later # that will block the logical apply worker on a lock. my $sub_session = $node_subscriber->background_psql('postgres'); +$sub_session->set_query_timer_restart(); # Test that when the logical apply worker is blocked on a lock and replication # is stalled, shutting down the publisher causes the logical walsender to exit -- 2.52.0