From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Inactive replication slots |
Date: | 2022-06-21 03:55:41 |
Message-ID: | CAMkU=1yEAW0qoNA0hjjmw0H3ddB-R3q9fadgRWWT6aBk=oX75g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Jun 20, 2022 at 3:12 PM Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Teja Jakkidi | 2022-06-21 05:27:46 | Re: Inactive replication slots |
Previous Message | Teja Jakkidi | 2022-06-20 19:12:47 | Inactive replication slots |