i guess he is trying to confirm if the value of max_replication_slot is the same on all the master and the standby nodes.
Regards,
also,
I am trying to shoot in the dark.
can you give the output of (on master)
ls /var/lib/postgresql/<pg_version>/main/pg_replslot/*
also the value of max_replication_slot on the master and all the standby's.
also, how are you creating the replication slot?
can you share the query?
also pls share the content of the recovery.conf on the standby nodes (both currently running and currently not running).
you can scribble company secret stuff.
Vijay
On Mon, Oct 15, 2018 at 1:58 AM bhargav kamineni <bhargavpostgres@xxxxxxxxx> wrote:
I got his on standby, could you please explain in detail about--but that *on the standby* haven't set max_replication_slots high enough.Thanks,BhargavOn Mon, 15 Oct 2018 at 01:50, Andres Freund <andres@xxxxxxxxxxx> wrote:Hi,
On 2018-10-15 00:15:53 +0530, bhargav kamineni wrote:
> Hi Team,
>
> I am getting this ERROR while starting my second slave server
>
> PANIC: too many replication slots active before shutdown
> HINT: Increase max_replication_slots and try again.
>
> max_replication_slots on my master is 2 and one of them is already active
> for another slave,
> do i need to increase this parameter for the need of working of another
> slave ? if so whats the reason ?
You're getting that error on the standby, not the primary, right? In
all likelihood the problem is that you copied over replication slots to
your standby server, but that *on the standby* haven't set
max_replication_slots high enough.
Greetings,
Andres Freund
