Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 52e7574

Browse files
committed
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
1 parent 2a8e1ac commit 52e7574

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

doc/src/sgml/high-availability.sgml

+8-3
Original file line numberDiff line numberDiff line change
@@ -1889,9 +1889,14 @@ if (!triggered)
18891889
situation will be no worse than if the standby queries were running
18901890
directly on the primary server, and you are still getting the benefit of
18911891
off-loading execution onto the standby.
1892-
<varname>max_standby_archive_delay</> must be kept large in this case,
1893-
because delayed WAL files might already contain entries that conflict with
1894-
the desired standby queries.
1892+
If standby servers connect and disconnect frequently, you
1893+
might want to make adjustments to handle the period when
1894+
<varname>hot_standby_feedback</> feedback is not being provided.
1895+
For example, consider increasing <varname>max_standby_archive_delay</>
1896+
so that queries are not rapidly cancelled by conflicts in WAL archive
1897+
files during disconnected periods. You should also consider increasing
1898+
<varname>max_standby_streaming_delay</> to avoid rapid cancellations
1899+
by newly-arrived streaming WAL entries after reconnection.
18951900
</para>
18961901

18971902
<para>

0 commit comments

Comments
 (0)