Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: 'replication checkpoint has wrong magic' on the newly cloned
 replicas
From: Oleksii Kliukin <oleksii@fastmail.com>
In-Reply-To: <20171129145455.GL4628@tamriel.snowman.net>
Date: Wed, 29 Nov 2017 18:41:24 +0100
Cc: pgsql-admin@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFFC01E6-FE97-4490-8D39-903BB910AB85@fastmail.com>
References: 
 <1511966240.1459861.1188109744.2D26AD08@webmail.messagingengine.com>
 <20171129145455.GL4628@tamriel.snowman.net>
To: Stephen Frost <sfrost@snowman.net>
Precedence: bulk

Hi Stephen,=20

> On 29. Nov 2017, at 15:54, Stephen Frost <sfrost@snowman.net> wrote:
>=20
> Greetings,
>=20
> * Alex Kliukin (alexk@hintbits.com) wrote:
>> The cloning itself is done by copying a compressed image via ssh,
>> running the
>> following command from the replica:
>>=20
>> """ssh {master} 'cd {master_datadir} && tar -lcp --exclude "*.conf" \
>>         --exclude "recovery.done" \
>>         --exclude "pacemaker_instanz" \
>>         --exclude "dont_start" \
>>         --exclude "pg_log" \
>>         --exclude "pg_xlog" \
>>         --exclude "postmaster.pid" \
>>         --exclude "recovery.done" \
>>           * | pigz -1 -p 4' | pigz -d -p 4 | tar -xpmUv -C
>>           {slave_datadir}""
>>=20
>> The WAL archiving starts before the copy starts, as the script that
>> clones the
>> replica checks that the WALs archiving is running before the cloning.
>=20
> Maybe you've doing it and haven't mentioned it, but you have to use
> pg_start/stop_backup

Sorry for not mentioning it, as it seemed obvious, but we are calling pg_sta=
rt_backup and pg_stop_backup at the right time.

Cheers,
Alex=