From: Samed YILDIRIM <samed@reddoc.net>
To: Marcin Koziej <marcin@cahoots.pl>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
Date: Wed, 25 Oct 2017 20:30:14 +0300
Message-ID: <1070071508952614@web46j.yandex.ru> (raw)
In-Reply-To: <d90474b1-6913-f3ff-d224-73fd931cdd98@cahoots.pl>
References: <d90474b1-6913-f3ff-d224-73fd931cdd98@cahoots.pl>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
<div>Hi Marcin,</div><div> </div><div>Could you please share archive_command and restore_command you used? If you are using script inside restore or archive comman, please also share them. It looks like the problem relevant with them.</div><div> </div><div>Best regards.</div><div>Samed YILDIRIM</div><div> </div><div> </div><div>25.10.2017, 19:52, "Marcin Koziej" <marcin@cahoots.pl>:</div><blockquote type="cite"><p>Hi!<br /><br />I try to setup continuous archiving with PG 9.6 according to this<br />documentation:<br /><a href="https://www.postgresql.org/docs/9.6/static/continuous-archiving.html">https://www.postgresql.... /><br />I have Postgres wal_archive set to replica, I have archive on and<br />archive command is properly copying WAL segments to backup storage.<br /><br />Having this running, I make a successful tar base backup using<br />pg_basebackup.<br /><br />I then stop the DB, remove the data directory, unpack base backup to it,<br />create recovery.conf with a proper restore_command, run the server, and get:<br /><br />LOG: database system was interrupted; last known up at <span>2017-10-25</span><br />15:47:37 UTC<br />LOG: starting archive recovery<br />Object 'pg_small3/pg_xlog/RECOVERYXLOG.lzo' not found<br />Cannot download pg_xlog/RECOVERYXLOG.lzo<br />LOG: invalid checkpoint record<br />FATAL: could not locate required checkpoint record<br />HINT: If you are not restoring from a backup, try removing the file<br />"/var/lib/postgresql/data/backup_label".<br />LOG: startup process (PID 20) exited with exit code 1<br />LOG: aborting startup due to startup process failure<br />LOG: database system is shut down<br /><br />The message about "pg_xlog/RECOVERYXLOG.lzo" is written out by<br />restore_command. Indeed, the file is not in the backup storage, and<br />pg_xlog/RECOVERYXLOG was NEVER sent there by archive_command (which<br />compresses and adds .lzo extension)!<br /><br />What could I be doing wrong?<br /> </p><span>--<br />Marcin Koziej </span><p><br />GPG key: <a href="http://go.cahoots.pl/gpg/">http://go.cahoots.pl/gpg/</a; Ϟ Twitter: @movonw<br /><br /><br /><br /> </p><span>--<br />Sent via pgsql-admin mailing list (<a href="mailto:pgsql-admin@postgresql.org">pgsql-admin@postgresql.org</a>)<br />To make changes to your subscription:<br /><a href="http://www.postgresql.org/mailpref/pgsql-admin">http://www.postgresql.org/mailpref/pgsql-admi...;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: samed@reddoc.net, marcin@cahoots.pl
Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
In-Reply-To: <1070071508952614@web46j.yandex.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox