| From: | Jayson Hreczuck <jayson(dot)hreczuck(at)studentuniverse(dot)com> |
|---|---|
| To: | Yambu <hyambu(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Order of removing logical replication |
| Date: | 2021-04-23 13:37:36 |
| Message-ID: | CAHg7=h6X+AuLv3-PrvoUDL_j_oWra8bnxY6ZTZsy6iSj3wM4VA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
That's the order but it's logical replication, and wouldn't interfere with
your master even if you ran it out of order.
I have 12 databases doing logical shipping to our subscription server and
occasionally it breaks but the master is never affected. When you restart
the subs there will be some I/O due to data shipping however.
Since we are talking about logical rep: What I would LOVE is schema change
support for the logical replication!
On Fri, Apr 23, 2021, 9:23 AM Yambu <hyambu(at)gmail(dot)com> wrote:
> Hello
>
> May i know in which order i have to stop logical replication without
> causing issues on postgres
>
> 1. drop subscription on slave
> 2. drop slot on master
>
> regards
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Silva | 2021-04-24 15:20:24 | xPath in a database with LATIN1 encoding |
| Previous Message | Yambu | 2021-04-23 13:23:04 | Order of removing logical replication |