postgres.git / summary / log / commit / refs

commit    2f8d6369e60a244f28e0c93b8a02e73758322915
Author:   Fujii Masao <fujii@postgresql.org>
Date:     Thu Nov 23 07:46:42 2017 +0000
First released in: 11.0, 10.2

    doc: mention wal_receiver_status_interval as GUC affecting logical rep worker.
    
    wal_receiver_timeout, wal_receiver_status_interval and
    wal_retrieve_retry_interval configuration parameters affect the logical rep
    worker, but previously only wal_receiver_status_interval was not mentioned
    as such parameter in the doc.
    
    Back-patch to v10 where logical rep was added.
    
    Author: Masahiko Sawada
    Discussion: https://www.postgresql.org/message-id/CAD21AoBUnuH_UsnKXyPCsCR7EAMamW0sSb6a7=WgiQRpnMAp5w@mail.gmail.com


 doc/src/sgml/config.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index fc1752fb3f1..7059dd4e5f5 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3410,7 +3410,8 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
      </para>
 
      <para>
-      Note that <varname>wal_receiver_timeout</varname> and
+      Note that <varname>wal_receiver_timeout</varname>,
+      <varname>wal_receiver_status_interval</varname> and
       <varname>wal_retrieve_retry_interval</varname> configuration parameters
       affect the logical replication workers as well.
      </para>


[parent: de0aca6a82af]