diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-22 11:10:12 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-12-22 11:10:12 -0500 |
commit | 08dde1b3dc78e90e01f3af8e89ab27ed37cd8963 (patch) | |
tree | 086ecc3628043630625382487481d77810a5902a /src | |
parent | 1ca2eb103113d64930cf1120ba2beaaebd1076f4 (diff) | |
download | postgresql-08dde1b3dc78e90e01f3af8e89ab27ed37cd8963.tar.gz postgresql-08dde1b3dc78e90e01f3af8e89ab27ed37cd8963.zip |
Increase timeout in 021_row_visibility.pl.
Commit 7b28913bc figured 30 seconds is long enough for anybody,
but in contexts like valgrind runs, it isn't necessarily.
Diffstat (limited to 'src')
-rw-r--r-- | src/test/recovery/t/021_row_visibility.pl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/recovery/t/021_row_visibility.pl b/src/test/recovery/t/021_row_visibility.pl index 8a466e56e0f..fac6646a872 100644 --- a/src/test/recovery/t/021_row_visibility.pl +++ b/src/test/recovery/t/021_row_visibility.pl @@ -33,7 +33,7 @@ $node_standby->start; # instance being driven by us, add a timeout high enough that it # should never trigger even on very slow machines, unless something # is really wrong. -my $psql_timeout = IPC::Run::timer(30); +my $psql_timeout = IPC::Run::timer(300); # One psql to primary and standby each, for all queries. That allows # to check uncommitted changes being replicated and such. |