pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

Inactive replication slots
3+ messages / 2 participants
[nested] [flat]

* Inactive replication slots
@ 2022-06-20 19:12  Teja Jakkidi <teja.jakkidi05@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Teja Jakkidi @ 2022-06-20 19:12 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org

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?
I tried restarting both primary and standby but sis not have any effect. 

Thanks and Regards,
J. Teja Sri.




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Inactive replication slots
@ 2022-06-21 03:55  Jeff Janes <jeff.janes@gmail.com>
  parent: Teja Jakkidi <teja.jakkidi05@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Jeff Janes @ 2022-06-21 03:55 UTC (permalink / raw)
  To: Teja Jakkidi <teja.jakkidi05@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>

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

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Inactive replication slots
@ 2022-06-21 05:27  Teja Jakkidi <teja.jakkidi05@gmail.com>
  parent: Jeff Janes <jeff.janes@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Teja Jakkidi @ 2022-06-21 05:27 UTC (permalink / raw)
  To: Jeff Janes <jeff.janes@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>

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

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2022-06-21 05:27 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-06-20 19:12 Inactive replication slots Teja Jakkidi <teja.jakkidi05@gmail.com>
2022-06-21 03:55 ` Jeff Janes <jeff.janes@gmail.com>
2022-06-21 05:27   ` Teja Jakkidi <teja.jakkidi05@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox