Commitc267ca6

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 parentf927767 commitc267ca6Copy full SHA for c267ca6

File tree

+16

-5

lines changed

+16

-5

lines changed

Lines changed: 11 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -3781,6 +3781,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows`
`3781`	`3781`	`to <literal>replica</literal> or higher to allow replication slots to`
`3782`	`3782`	`be used.`
`3783`	`3783`	`</para>`
	`3784`	`+`
	`3785`	`+ <para>`
	`3786`	`+ On the subscriber side, specifies how many replication origins (see`
	`3787`	`+ <xref linkend="replication-origins"/>) can be tracked simultaneously,`
	`3788`	`+ effectively limiting how many logical replication subscriptions can`
	`3789`	`+ be created on the server. Setting it a lower value than the current`
	`3790`	`+ number of tracked replication origins (reflected in`
	`3791`	`+ <link linkend="view-pg-replication-origin-status">pg_replication_origin_status</link>,`
	`3792`	`+ not <link linkend="catalog-pg-replication-origin">pg_replication_origin</link>)`
	`3793`	`+ will prevent the server from starting.`
	`3794`	`+ </para>`
`3784`	`3795`	`</listitem>`
`3785`	`3796`	`</varlistentry>`
`3786`	`3797`

Lines changed: 5 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -577,11 +577,11 @@`
`577`	`577`
`578`	`578`	`<para>`
`579`	`579`	`The subscriber also requires the <varname>max_replication_slots</varname>`
`580`		`-tobe set. In this case it shouldbeset to at least the number of`
`581`		`-subscriptions that will beadded to thesubscriber.`
`582`		`- <varname>max_logical_replication_workers</varname> must be set to at`
`583`		`- least the number of subscriptions, again plus some reserve for the table`
`584`		`- synchronization. Additionally the <varname>max_worker_processes</varname>`
	`580`	`+ be set to configure how many replication origins canbetracked. In this`
	`581`	`+case it should beset toat leastthenumber of subscriptions that will be`
	`582`	`+added to the subscriber.<varname>max_logical_replication_workers</varname>`
	`583`	`+must be set to atleast the number of subscriptions, again plus some reserve`
	`584`	`+for the tablesynchronization. Additionally the <varname>max_worker_processes</varname>`
`585`	`585`	`may need to be adjusted to accommodate for replication workers, at least`
`586`	`586`	`(<varname>max_logical_replication_workers</varname>`
`587`	`587`	`+ <literal>1</literal>). Note that some extensions and parallel queries`

Comments

(0)