We think we have found our missing step. We needed to do an ordered shutdown of
the original primary before promoting the standby
I.e.
>1. Make some changes to the A (the primary) and check that they are replicated
>to the B (the standby)
Missing step:
Perform ordered shutdown of A (the pr
> Now once your master A can’t become slave of B.
Isn’t that the exact situation that pg_rewind should take care of?
This email and any attachments may contain confidential information. If you are
not the intended recipient, your use or communication of the information is
strictly prohibited.
We have been struggling to get pr_rewind to work. In desperation we have been
trying to make the use case as simple as possible:)
We have two databases servers running Postgres 10 on two different machine in
the normal Primary/Standby configuration.
Both machines write their WAL archive logs to
