forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit2710ccd
committed
Reduce wal_retrieve_retry_interval in applicable TAP tests.
By default, wal_retrieve_retry_interval is five seconds, which is farmore than is needed in any of our TAP tests, leaving the test casesjust 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 upwal_retrieve_retry_interval = '500ms' as part of its customization oftest clusters' postgresql.conf. This shaves quite a few seconds offthe 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.us1 parente5d494d commit2710ccd
1 file changed
+1
-0
lines changedLines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
414 | 414 | | |
415 | 415 | | |
416 | 416 | | |
| 417 | + | |
417 | 418 | | |
418 | 419 | | |
419 | 420 | | |
| |||
0 commit comments
Comments
(0)