aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2025-03-31 16:54:50 +0200
committerPeter Eisentraut <peter@eisentraut.org>2025-03-31 16:54:50 +0200
commit0fcf02ad456862d8523a1918e2882e7697a52896 (patch)
treec1fac3e9930e316a19ae441d9c4e83ccd16fa4ee /doc/src
parente2809e3a1015697832ee4d37b75ba1cd0caac0f0 (diff)
downloadpostgresql-0fcf02ad456862d8523a1918e2882e7697a52896.tar.gz
postgresql-0fcf02ad456862d8523a1918e2882e7697a52896.zip
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
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 0d02e21a1ab..fea683cb49c 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5068,6 +5068,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
until it eventually reaches the primary. Standbys make no other use
of feedback they receive other than to pass upstream.
</para>
+ <para>
+ Note that if the clock on standby is moved ahead or backward, the
+ feedback message might not be sent at the required interval. In
+ extreme cases, this can lead to a prolonged risk of not removing dead
+ rows on the primary for extended periods, as the feedback mechanism is
+ based on timestamps.
+ </para>
</listitem>
</varlistentry>