mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Fix some issues in logical replication section

Browse Source 
wal_retrieve_retry_interval was mentioned under an incorrect name, and
wal_sender_timeout was not listed as affecting WAL senders in logical
replication mode.

Author: Takamichi Osumi
Discussion: https://postgr.es/m/TYCPR01MB8373D65E6B0A769ED12EADCBEDC79@TYCPR01MB8373.jpnprd01.prod.outlook.com
This commit is contained in:
Michael Paquier 2023-01-19 14:00:23 +09:00
parent 7e8a80d1fe
commit 4f74f5641d
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/logical-replication.sgml
View File

@ -1807,6 +1807,11 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
replicas that are connected at the same time.
</para>
<para>
Logical replication walsender is also affected by
<link linkend="guc-wal-sender-timeout"><varname>wal_sender_timeout</varname></link>.
</para>
</sect2>
<sect2 id="logical-replication-config-subscriber">
@ -1850,7 +1855,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
Logical replication workers are also affected by
<link linkend="guc-wal-receiver-timeout"><varname>wal_receiver_timeout</varname></link>,
<link linkend="guc-wal-receiver-status-interval"><varname>wal_receiver_status_interval</varname></link> and
<link linkend="guc-wal-retrieve-retry-interval"><varname>wal_receiver_retry_interval</varname></link>.
<link linkend="guc-wal-retrieve-retry-interval"><varname>wal_retrieve_retry_interval</varname></link>.
</para>
</sect2>