From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Samed YILDIRIM <samed(at)reddoc(dot)net> |
Cc: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Best way to stop Streaming Replication? |
Date: | 2023-12-23 23:53:03 |
Message-ID: | CANzqJaAyBe7E7yRMMVYsRoYOTgxi2_SH+A0SyKbs11JbWpS8ig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Dec 23, 2023
> If you already have a replication created with a replication slot, then,
> you can clean restore_command and primary_conninfo settings on replica,
> reload configuration of the replica, and then remove the leftover
> replication slot from the master. For example:
>
> - on replica
> - alter system set primary_conninfo to '';
> - alter system set restore_command to '';
> - select pg_reload_conf();
> - on master
> - select pg_drop_replication_slot('ron_replication_slot1');
>
> Excellent. Thank you
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2023-12-24 14:00:04 | Re: Need inputs on postgresql HA with consul cluster |
Previous Message | Samed YILDIRIM | 2023-12-23 22:57:23 | Re: Best way to stop Streaming Replication? |