postgres.git / summary / log / commit / refs

commit    7cda7b50d562a03f1c2e0c1d2f2e970acbd769e8
Author:   Daniel Gustafsson <dgustafsson@postgresql.org>
Date:     Wed Aug 12 07:41:44 2026 +0000

    Use per-query timeout in subscription test
    
    A buildfarm failure in subscription/038_walsnd_shutdown_timeout was
    diagnosed to the background psql session timing out due to a backup
    taking a long time.  The session was using a single timeout for all
    queries, so switch to resetting the timer for each query to make it
    survive slow backups due to constrained buildfarm machines.
    
    Backpatch to v19 where the test was introduced.
    
    Author: Hayato Kuroda <kuroda.hayato@fujitsu.com>
    Discussion: https://postgr.es/m/OS9PR01MB12149AA18EEA475D2AA22FD3BF5D12@OS9PR01MB12149.jpnprd01.prod.outlook.com
    Backpatch-through: 19


 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


[parent: 7ff4ee83f7ae]