Re: 'replication checkpoint has wrong magic' on the newly clonedreplicas - Mailing list pgsql-admin

From Alvaro Herrera
Subject Re: 'replication checkpoint has wrong magic' on the newly clonedreplicas
Date
Msg-id 20171129232243.vk5ik5szknppo3it@alvherre.pgsql
Whole thread Raw
In response to 'replication checkpoint has wrong magic' on the newly cloned replicas  (Alex Kliukin <alexk@hintbits.com>)
Responses Re: 'replication checkpoint has wrong magic' on the newly clonedreplicas  (Andres Freund <andres@anarazel.de>)
Re: 'replication checkpoint has wrong magic' on the newly clonedreplicas  (Alex Kliukin <alexk@hintbits.com>)
List pgsql-admin
Alex Kliukin wrote:

> 2017-11-15 13:15:46.673 CET,,,15154,,5a0c2ff1.3b32,5,,2017-11-15
> 13:15:45 CET,,0,PANIC,XX000,"replication checkpoint has wrong magic
> 5714534 instead of 307747550",,,,,,,,,""

Uhh ... I had never heard of this "replication checkpoint" thing.  It is
part of replication origins feature, which is fairly new stuff (see
src/backend/replication/logical/origin.c).  I'd bet this problem is
related to a bug in logical replication "origins" code rather than any
procedural problems in your base-backup taking setup ...

I wonder if there is some truncation of the 0x1257DADE value that
produces the 5714534 value you're seeing -- something related to a
pg_logical/replorigin_checkpoint file being written partially while the
backup is being taken.

Another point towards not including pg_logical/ contents when taking a
base backup, I guess ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-admin by date:

Previous
From: Sean G
Date:
Subject: Re: Barman WAL size issue
Next
From: Andres Freund
Date:
Subject: Re: 'replication checkpoint has wrong magic' on the newly clonedreplicas