database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-05 09:19:17 +03:00
Code

Reduce wal_retrieve_retry_interval in applicable TAP tests.

Browse Source 
By default, wal_retrieve_retry_interval is five seconds, which is far
more than is needed in any of our TAP tests, leaving the test cases
just twiddling their thumbs for significant stretches.  Moreover,
because it's so large, we get basically no testing of the retry-before-
master-is-ready code path.  Hence, make PostgresNode::init set up
wal_retrieve_retry_interval = '500ms' as part of its customization of
test clusters' postgresql.conf.  This shaves quite a few seconds off
the runtime of the recovery TAP tests.

Back-patch into 9.6.  We have wal_retrieve_retry_interval in 9.5,
but the test infrastructure isn't there.

Discussion: https://postgr.es/m/31624.1498500416@sss.pgh.pa.us
This commit is contained in:
Tom Lane 2017-06-26 19:01:26 -04:00
parent a4d1ce095b
commit df31a9fc66
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/test/perl/PostgresNode.pm
View File

@ -413,6 +413,7 @@ sub init
print $conf "fsync = off\n"; print $conf "fsync = off\n";
print $conf "restart_after_crash = off\n"; print $conf "restart_after_crash = off\n";
print $conf "log_statement = all\n"; print $conf "log_statement = all\n";
print $conf "wal_retrieve_retry_interval = '500ms'\n";
print $conf "port = $port\n"; print $conf "port = $port\n";
if ($params{allows_streaming}) if ($params{allows_streaming})