mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: adjustments for streaming standbys that disconnect frequently

Browse Source 
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
This commit is contained in:
Bruce Momjian 2014-04-17 10:52:32 -04:00
parent 2a8e1ac598
commit 52e757420f
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/sgml/high-availability.sgml
View File

@ -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>