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

Commit f3a5e1c

Browse files
jakubwartakEDBCommitfest Bot
authored and
Commitfest Bot
committed
doc: Mention clock synchronization recommendation for hot_standby_feedback
hot_standby_feedback mechanics assume that clocks are synchronized, but it was not clear from documentation. Discussion: https://postgr.es/m/CAKZiRmwBcALLrDgCyEhHP1enUxtPMjyNM_d1A2Lng3_6Rf4Qfw%40mail.gmail.com
1 parent 058b515 commit f3a5e1c

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

doc/src/sgml/config.sgml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5068,6 +5068,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
50685068
until it eventually reaches the primary. Standbys make no other use
50695069
of feedback they receive other than to pass upstream.
50705070
</para>
5071+
<para>
5072+
Note that if the clock on standby is moved ahead or backward, the
5073+
feedback message may not be sent at the required interval. In extreme
5074+
cases this can lead to prolonged risk of not removing dead rows on
5075+
primary for extended periods as the feedback mechanism is based on
5076+
timestamp.
5077+
</para>
50715078
</listitem>
50725079
</varlistentry>
50735080

0 commit comments

Comments
 (0)