| From: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Best way to stop Streaming Replication? |
| Date: | 2023-12-22 21:11:32 |
| Message-ID: | CA+427g9yfibEe62upmOnW7On6ixwvQbXXiLLPwT8vKAQ9p3bYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Use a some tools like patroni. I'm patroni user since 2016 and happy with
it.
br
Kaido
On Fri, 22 Dec 2023, 21:49 Ron Johnson, <ronljohnsonjr(at)gmail(dot)com> wrote:
> PG 14.10 and 15.5, if it matters.
>
> Running pg_terminate_backend() on the walsender pid (and then dropping the
> replication slot) seems the canonical solution, based on StackExchange, but
> that leaves primary_conninfo in postgresql.auto.conf and standby.signal in
> $PGDATA.
>
> Promoting the secondary (and then dropping the replication slot) handles
> all those issues, but leaves it in R/W mode, which might cause split brain
> issues with cluster managers.
>
> Is there a better way than the two I've described
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samed YILDIRIM | 2023-12-22 21:38:05 | Re: Best way to stop Streaming Replication? |
| Previous Message | Ron Johnson | 2023-12-22 19:49:34 | Best way to stop Streaming Replication? |