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!
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
Есть вопросы? Напишите нам!
✖
Чтобы сделать работу с сайтом удобнее, мы используем cookie и аналитический сервис «Яндекс.Метрика». Продолжая пользоваться сайтом, вы соглашаетесь с их использованием.