diff options
| author | Bruce Momjian | 2014-04-17 14:52:32 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2014-04-17 14:52:48 +0000 |
| commit | 52e757420fa98a76015c2c88432db94269f3e8f4 (patch) | |
| tree | c3c23f2649d64cb4ddbf818d315d3ec1809d2393 | |
| parent | 2a8e1ac598c864ac2775f33da21a117c363c6c7f (diff) | |
docs: adjustments for streaming standbys that disconnect frequently
Document problems when disconnection causes loss of hot_standby_feedback
and suggest adjusting max_standby_archive_delay and
max_standby_streaming_delay.
Initial patch by Marko Tiikkaja, adjustments by me
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index ecb51c4b1a2..39d7467ddd1 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1889,9 +1889,14 @@ if (!triggered) situation will be no worse than if the standby queries were running directly on the primary server, and you are still getting the benefit of off-loading execution onto the standby. - <varname>max_standby_archive_delay</> must be kept large in this case, - because delayed WAL files might already contain entries that conflict with - the desired standby queries. + If standby servers connect and disconnect frequently, you + might want to make adjustments to handle the period when + <varname>hot_standby_feedback</> feedback is not being provided. + For example, consider increasing <varname>max_standby_archive_delay</> + so that queries are not rapidly cancelled by conflicts in WAL archive + files during disconnected periods. You should also consider increasing + <varname>max_standby_streaming_delay</> to avoid rapid cancellations + by newly-arrived streaming WAL entries after reconnection. </para> <para> |