From: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Inactive replication slots |
Date: | 2022-06-21 05:27:46 |
Message-ID: | C995B34F-A607-48D8-AB3C-BC8CF9A495C6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(dot)janes(at)gmail(dot)com> wrote:
>
>
>> 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 | Fabio Pardi | 2022-06-21 05:38:17 | Re: parallel index creation: maintenance_work_mem not honored? |
Previous Message | Jeff Janes | 2022-06-21 03:55:41 | Re: Inactive replication slots |