Commit4f74f56

committed

doc: Fix some issues in logical replication section

wal_retrieve_retry_interval was mentioned under an incorrect name, andwal_sender_timeout was not listed as affecting WAL senders in logicalreplication mode.Author: Takamichi OsumiDiscussion:https://postgr.es/m/TYCPR01MB8373D65E6B0A769ED12EADCBEDC79@TYCPR01MB8373.jpnprd01.prod.outlook.com

1 parent7e8a80d commit4f74f56Copy full SHA for 4f74f56

File tree

-1

lines changed

-1

lines changed

Lines changed: 6 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1807,6 +1807,11 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER`
`1807`	`1807`	`replicas that are connected at the same time.`
`1808`	`1808`	`</para>`
`1809`	`1809`
	`1810`	`+ <para>`
	`1811`	`+ Logical replication walsender is also affected by`
	`1812`	`+ <link linkend="guc-wal-sender-timeout"><varname>wal_sender_timeout</varname></link>.`
	`1813`	`+ </para>`
	`1814`	`+`
`1810`	`1815`	`</sect2>`
`1811`	`1816`
`1812`	`1817`	`<sect2 id="logical-replication-config-subscriber">`
`@@ -1850,7 +1855,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER`
`1850`	`1855`	`Logical replication workers are also affected by`
`1851`	`1856`	`<link linkend="guc-wal-receiver-timeout"><varname>wal_receiver_timeout</varname></link>,`
`1852`	`1857`	`<link linkend="guc-wal-receiver-status-interval"><varname>wal_receiver_status_interval</varname></link> and`
`1853`		`- <link linkend="guc-wal-retrieve-retry-interval"><varname>wal_receiver_retry_interval</varname></link>.`
	`1858`	`+ <link linkend="guc-wal-retrieve-retry-interval"><varname>wal_retrieve_retry_interval</varname></link>.`
`1854`	`1859`	`</para>`
`1855`	`1860`
`1856`	`1861`	`</sect2>`

Comments

(0)