Thread: Inactive replication slots
Hello Everyone, I have a primary Postgres server with 2 standbys setup using streaming replication. Both the stand by servers are using thereplication slots. Today, when I checked the status of replication slots on primary, they are showing active= ‘f’. The data is replicating withno issues but when the slots are inactive I know that the wal files generated after the restart_lsn will not be deletedand retains the transactions, which is very critical. I am not sure exactly why the slots are inactive and if there is a way to activate them back? I tried restarting both primary and standby but sis not have any effect. Thanks and Regards, J. Teja Sri.
On Mon, Jun 20, 2022 at 3:12 PM Teja Jakkidi <teja.jakkidi05@gmail.com> wrote:
Hello Everyone,
I have a primary Postgres server with 2 standbys setup using streaming replication. Both the stand by servers are using the replication slots.
Today, when I checked the status of replication slots on primary, they are showing active= ‘f’. The data is replicating with no issues but when the slots are inactive I know that the wal files generated after the restart_lsn will not be deleted and retains the transactions, which is very critical.
I am not sure exactly why the slots are inactive and if there is a way to activate them back?
Is primary_slot_name set on each replica?
Cheers,
Jeff
Hi Jeff,
You are correct. That is what was missing on replica servers. When I set that parameter, slots were active automatically. Thank you.
Regards,
Teja.
Thanks and Regards,
J. Teja Sri.
On Jun 20, 2022, at 8:55 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
On Mon, Jun 20, 2022 at 3:12 PM Teja Jakkidi <teja.jakkidi05@gmail.com> wrote:Hello Everyone,
I have a primary Postgres server with 2 standbys setup using streaming replication. Both the stand by servers are using the replication slots.
Today, when I checked the status of replication slots on primary, they are showing active= ‘f’. The data is replicating with no issues but when the slots are inactive I know that the wal files generated after the restart_lsn will not be deleted and retains the transactions, which is very critical.
I am not sure exactly why the slots are inactive and if there is a way to activate them back?Is primary_slot_name set on each replica?Cheers,Jeff