Hi,
When pg_rewind is interrupted due to network errors, the cluster gets
corrupted:
Running pg_rewind for a second time returns "pg_rewind: fatal: target
server must be shut down cleanly".
Trying to fix the cluster with "/usr/pgsql-12/bin/postmaster' --single
-F -D
Hello,
I've created synchronous replication between Primary and Secondary server and
put pacemaker + PAF over. Client is doing some stress tests (switching nodes,
disabling particular node, etc) and it's second time when this kind of problem
occoures :
2020-12-18 14:03:46.658 CET [unknown]
On 12/20/20 8:33 AM, Lars Vonk wrote:
Hi,
Just wondering if someone knows how this could have happened? Did we
miss out on something when setting up the logical replication? Are there
any scenario's in which this could happen (like database restart or
anything else?).
Or should I report
Hi,
Just wondering if someone knows how this could have happened? Did we miss
out on something when setting up the logical replication? Are there any
scenario's in which this could happen (like database restart or anything
else?).
Or should I report this a bug (although I can't image it is)?
We
