That's a good trick, thanks again for the help.
Boy, this promises to be a dumb process! I'm unqualified to guess at
what might make this easier, but it does seem like something that
should have some kind of low-level tools that could do the job.
On Wed, Jan 8, 2020 at 1:53 AM Laurenz Albe wrote
On Tue, 2020-01-07 at 23:17 -0800, Mike Lissner wrote:
> > You'd have to suspend all data modification on A in that interval.
>
> I know how to stop the DB completely, but I can't think of any obvious
> ways to make sure that it doesn't get any data modification for a
> period of time. Is there a
> You'd have to suspend all data modification on A in that interval.
I know how to stop the DB completely, but I can't think of any obvious
ways to make sure that it doesn't get any data modification for a
period of time. Is there a trick here? This is feeling a bit hopeless.
Thanks for the respo
On Tue, 2019-12-31 at 15:51 -0800, Mike Lissner wrote:
> Hi, I'm trying to figure out how to shorten a chain of logically
> replicating servers. Right now we have three servers replicating like
> so:
>
> A --> B --> C
>
> And I'd like to remove B from the chain of replication so that I only have:
Hi, I don't usually like to bump messages on this list, but since I
sent mine on New Year's Eve, I figured I'd better. Anybody have any
ideas about how to accomplish this? I'm pretty stumped (as you can
probably see).
On Tue, Dec 31, 2019 at 3:51 PM Mike Lissner
wrote:
>
> Hi, I'm trying to figur
Hi, I'm trying to figure out how to shorten a chain of logically
replicating servers. Right now we have three servers replicating like
so:
A --> B --> C
And I'd like to remove B from the chain of replication so that I only have:
A --> C
Of course, doing this without losing data is the goal. If
