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@xxxxxxxxx> wrote:
HelloMay i know in which order i have to stop logical replication without causing issues on postgres1. drop subscription on slave2. drop slot on masterregards
