Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit0fcf02a

Browse files
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.Author: Jakub Wartak <jakub.wartak@enterprisedb.com>Reviewed-by: Euler Taveira <euler@eulerto.com>Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>Reviewed-by: vignesh C <vignesh21@gmail.com>Discussion:https://postgr.es/m/CAKZiRmwBcALLrDgCyEhHP1enUxtPMjyNM_d1A2Lng3_6Rf4Qfw%40mail.gmail.com
1 parente2809e3 commit0fcf02a

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 might not be sent at the required interval. In
5074+
extreme cases, this can lead to a prolonged risk of not removing dead
5075+
rows on the primary for extended periods, as the feedback mechanism is
5076+
based on timestamps.
5077+
</para>
50715078
</listitem>
50725079
</varlistentry>
50735080

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp