Thread: [DOCS] max_replication_slots in subscriber for subscription?

[DOCS] max_replication_slots in subscriber for subscription?

From
jonny.battiato@gmail.com
Date:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/logical-replication-config.html
Description:

Hi!

In this section:
https://www.postgresql.org/docs/10/static/logical-replication-config.html

the following sentences make no sense in the way replication slots are
designed:

"The subscriber also requires the max_replication_slots to be set. In this
case it should be set to at least the number of subscriptions that will be
added to the subscriber."

I can understand if the subscriber would be used as a publisher as well, so
the second sentence could make more sense as follows:

"In this case it should be set to at least the number of publications that
will be added to the subscriber."

Could you please check?
And if I'm wrong, I would appreciate a little more clear explanation.


Many thanks,
Jonathan

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] max_replication_slots in subscriber for subscription?

From
Alvaro Herrera
Date:
jonny.battiato@gmail.com wrote:

> In this section:
> https://www.postgresql.org/docs/10/static/logical-replication-config.html
> 
> the following sentences make no sense in the way replication slots are
> designed:
> 
> "The subscriber also requires the max_replication_slots to be set. In this
> case it should be set to at least the number of subscriptions that will be
> added to the subscriber."
> 
> I can understand if the subscriber would be used as a publisher as well, so
> the second sentence could make more sense as follows:
> 
> "In this case it should be set to at least the number of publications that
> will be added to the subscriber."
> 
> Could you please check?
> And if I'm wrong, I would appreciate a little more clear explanation.

Apparently, the reason for this (and correct me if I'm wrong) is that
the maximum number of replication origins is determined from
max_replication_slots, too.  So the subscriber does not actually use any
slots, but it needs some replication origins, which is why you need to
increase the parameter.

This seems a little silly to me, but patching the server to add the new
variable is surely out of discussion for pg10.  Should we change it in
pg11?

Also, do we want to add a footnote explaining this?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs