Commit8af3c23

Amit Kapila

committed

Clarify the usage of max_replication_slots on the subscriber side.

It was not clear in the docs that the max_replication_slots is also usedto track replication origins on the subscriber side.Author: Paul MartinezReviewed-by: Amit KapilaBackpatch-through: 10 where logical replication was introducedDiscussion:https://postgr.es/m/CACqFVBZgwCN_pHnW6dMNCrOS7tiHCw6Retf_=U2Vvj3aUSeATw@mail.gmail.com

1 parente527a99 commit8af3c23Copy full SHA for 8af3c23

File tree

+17

-5

lines changed

+17

-5

lines changed

Lines changed: 11 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -4001,6 +4001,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows`
`4001`	`4001`	`to <literal>replica</literal> or higher to allow replication slots to`
`4002`	`4002`	`be used.`
`4003`	`4003`	`</para>`
	`4004`	`+`
	`4005`	`+ <para>`
	`4006`	`+ On the subscriber side, specifies how many replication origins (see`
	`4007`	`+ <xref linkend="replication-origins"/>) can be tracked simultaneously,`
	`4008`	`+ effectively limiting how many logical replication subscriptions can`
	`4009`	`+ be created on the server. Setting it a lower value than the current`
	`4010`	`+ number of tracked replication origins (reflected in`
	`4011`	`+ <link linkend="view-pg-replication-origin-status">pg_replication_origin_status</link>,`
	`4012`	`+ not <link linkend="catalog-pg-replication-origin">pg_replication_origin</link>)`
	`4013`	`+ will prevent the server from starting.`
	`4014`	`+ </para>`
`4004`	`4015`	`</listitem>`
`4005`	`4016`	`</varlistentry>`
`4006`	`4017`

Lines changed: 6 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -603,11 +603,12 @@`
`603`	`603`
`604`	`604`	`<para>`
`605`	`605`	`The subscriber also requires the <varname>max_replication_slots</varname>`
`606`		`- to be set. In this case it should be set to at least the number of`
`607`		`- subscriptions that will be added to the subscriber, plus some reserve for`
`608`		`- table synchronization. <varname>max_logical_replication_workers</varname>`
`609`		`- must be set to at least the number of subscriptions, again plus some reserve`
`610`		`- for the table synchronization. Additionally the <varname>max_worker_processes</varname>`
	`606`	`+ be set to configure how many replication origins can be tracked. In this`
	`607`	`+ case it should be set to at least the number of subscriptions that will be`
	`608`	`+ added to the subscriber, plus some reserve for table synchronization.`
	`609`	`+ <varname>max_logical_replication_workers</varname> must be set to at least`
	`610`	`+ the number of subscriptions, again plus some reserve for the table`
	`611`	`+ synchronization. Additionally the <varname>max_worker_processes</varname>`
`611`	`612`	`may need to be adjusted to accommodate for replication workers, at least`
`612`	`613`	`(<varname>max_logical_replication_workers</varname>`
`613`	`614`	`+ <literal>1</literal>). Note that some extensions and parallel queries`

Comments

(0)