Commit21d5a06

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 parentb52fd1e commit21d5a06Copy full SHA for 21d5a06

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
`@@ -3891,6 +3891,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows`
`3891`	`3891`	`to <literal>replica</literal> or higher to allow replication slots to`
`3892`	`3892`	`be used.`
`3893`	`3893`	`</para>`
	`3894`	`+`
	`3895`	`+ <para>`
	`3896`	`+ On the subscriber side, specifies how many replication origins (see`
	`3897`	`+ <xref linkend="replication-origins"/>) can be tracked simultaneously,`
	`3898`	`+ effectively limiting how many logical replication subscriptions can`
	`3899`	`+ be created on the server. Setting it a lower value than the current`
	`3900`	`+ number of tracked replication origins (reflected in`
	`3901`	`+ <link linkend="view-pg-replication-origin-status">pg_replication_origin_status</link>,`
	`3902`	`+ not <link linkend="catalog-pg-replication-origin">pg_replication_origin</link>)`
	`3903`	`+ will prevent the server from starting.`
	`3904`	`+ </para>`
`3894`	`3905`	`</listitem>`
`3895`	`3906`	`</varlistentry>`
`3896`	`3907`

Lines changed: 5 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -588,11 +588,11 @@`
`588`	`588`
`589`	`589`	`<para>`
`590`	`590`	`The subscriber also requires the <varname>max_replication_slots</varname>`
`591`		`-tobe set. In this case it shouldbeset to at least the number of`
`592`		`-subscriptions that will beadded to thesubscriber.`
`593`		`- <varname>max_logical_replication_workers</varname> must be set to at`
`594`		`- least the number of subscriptions, again plus some reserve for the table`
`595`		`- synchronization. Additionally the <varname>max_worker_processes</varname>`
	`591`	`+ be set to configure how many replication origins canbetracked. In this`
	`592`	`+case it should beset toat leastthenumber of subscriptions that will be`
	`593`	`+added to the subscriber.<varname>max_logical_replication_workers</varname>`
	`594`	`+must be set to atleast the number of subscriptions, again plus some reserve`
	`595`	`+for the tablesynchronization. Additionally the <varname>max_worker_processes</varname>`
`596`	`596`	`may need to be adjusted to accommodate for replication workers, at least`
`597`	`597`	`(<varname>max_logical_replication_workers</varname>`
`598`	`598`	`+ <literal>1</literal>). Note that some extensions and parallel queries`

Comments

(0)