postgres.git / summary / log / commit / refs

commit    2dcaebea079d6e3c2c78bbf3b0948bf5ef707e21
Author:   Noah Misch <noah@leadboat.com>
Date:     Thu Feb 11 01:34:57 2016 +0000

    In pg_rewind test suite, triple promote timeout to 90s.
    
    Thirty seconds was not consistently enough for promotion to complete on
    buildfarm members sungazer and tern.  Experiments suggest 43s would have
    been enough.  Back-patch to 9.5, where pg_rewind was introduced.


 src/bin/pg_rewind/RewindTest.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/bin/pg_rewind/RewindTest.pm b/src/bin/pg_rewind/RewindTest.pm
index d23ad2d00cd..426bd6e5cf3 100644
--- a/src/bin/pg_rewind/RewindTest.pm
+++ b/src/bin/pg_rewind/RewindTest.pm
@@ -130,7 +130,7 @@ sub poll_query_until
 {
 	my ($query, $connstr) = @_;
 
-	my $max_attempts = 30;
+	my $max_attempts = 90;
 	my $attempts     = 0;
 	my ($stdout, $stderr);
 
@@ -151,7 +151,7 @@ sub poll_query_until
 		$attempts++;
 	}
 
-	# The query result didn't change in 30 seconds. Give up. Print the stderr
+	# The query result didn't change in 90 seconds. Give up. Print the stderr
 	# from the last attempt, hopefully that's useful for debugging.
 	diag $stderr;
 	return 0;


[parent: 725f0ce29690]