postgres.git / summary / log / commit / refs

commit    d6d9b96b4044e5c744bf2c6474b2c5c2de355f85
Author:   Andrew Dunstan <andrew@dunslane.net>
Date:     Fri Feb 27 12:14:06 2026 +0000

    Clean up nodes that  are no longer of use in 007_pgdumpall.pl
    
    Oversight in commit 763aaa06f03. When nodes are going out of scope, we
    should stop the underlying postmasters rather than waiting for the
    script to end.
    
    Per gripe from Tom Lane
    
    Discussion: https://postgr.es/m/740033.1772142754@sss.pgh.pa.us


 src/bin/pg_dump/t/007_pg_dumpall.pl | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/bin/pg_dump/t/007_pg_dumpall.pl b/src/bin/pg_dump/t/007_pg_dumpall.pl
index b228e572f43..04eba494b4e 100644
--- a/src/bin/pg_dump/t/007_pg_dumpall.pl
+++ b/src/bin/pg_dump/t/007_pg_dumpall.pl
@@ -352,6 +352,9 @@ foreach my $run (sort keys %pgdumpall_runs)
 			$pgdumpall_runs{$run}->{unlike},
 			"should not dump $run");
 	}
+
+	$target_node->stop;
+	$target_node->clean_node;
 }
 
 # Some negative test case with dump of pg_dumpall and restore using pg_restore


[parent: 574bee89c237]