[CF 5425] v2 - doc: Mention clock synchronization recommendation for hot_standby_feedback

This branch was automatically generated by a robot using patches from an
email thread registered at:

https://commitfest.postgresql.org/patch/5425

The branch will be overwritten each time a new patch version is posted to
the thread, and also periodically to check for bitrot caused by changes
on the master branch.

Patch(es): https://www.postgresql.org/message-id/CAKZiRmyEBkR5tfwrzXaoC6D29Gp6g_fD6Bd_k58DjZV1=rbKdQ@mail.gmail.com
Author(s): Jakub Wartak

Author: Commitfest Bot

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 may not be sent at the required interval. In extreme
+        cases this can lead to prolonged risk of not removing dead rows on
+        primary for extended periods as the feedback mechanism is based on
+        timestamp.
+       </para>
       </listitem>
      </varlistentry>