pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
Date: Thu, 2 Nov 2017 17:23:07 +1300
Message-ID: <c37a48d3-05f0-9041-a586-fe7591c9154c@catalyst.net.nz> (raw)
In-Reply-To: <20171101221807.GW4628@tamriel.snowman.net>
References: <d90474b1-6913-f3ff-d224-73fd931cdd98@cahoots.pl>
	<1070071508952614@web46j.yandex.ru>
	<ae7f2ee9-97ff-267e-b6dc-9399250a9314@cahoots.pl>
	<20171030154706.GE4628@tamriel.snowman.net>
	<7966ee9e-2241-eced-4639-e32c157b915a@catalyst.net.nz>
	<20171031114756.GP4628@tamriel.snowman.net>
	<2e3453d3-da6f-88af-05ec-7530e7f60547@catalyst.net.nz>
	<20171101122847.GS4628@tamriel.snowman.net>
	<4efa2769-78c4-7bf0-5c33-0cf2d942ce74@catalyst.net.nz>
	<20171101221807.GW4628@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On 02/11/17 11:18, Stephen Frost wrote:

> Not having
> a way to reliably sync the WAL files copied by archive command to disk,
> in particular, really is an issue, it's not some feature, it's a
> requirement of a functional PG backup system.  The other requirement for
> a functional PG backup system is a check to verify that all of the WAL
> for a given backup has been archived safely to disk, otherwise the
> backup is incomplete and can't be used.
>
>

Funnily enough, the original poster's scripts were attempting to address 
(at least some) of this: he was sending stuff to swift, so if he got a 
ok return code then it is *there* - that being the whole point of a 
distributed, fault tolerant object store (I do swift support BTW).

I wonder if you are seeing this discussion in the light of folk doing 
backups to unreliable storage locations (e.g: the same server, NFS etc 
etc), then sure I completely agree with what you are saying (these issue 
impact backup designs no matter what tool is used to write them).

Best wishes

Mark


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (18+ messages)  latest in thread

Message-ID: <c37a48d3-05f0-9041-a586-fe7591c9154c@catalyst.net.nz>
Permalink:  ../c37a48d3-05f0-9041-a586-fe7591c9154c@catalyst.net.nz/
Also on:    postgresql.org/message-id/c37a48d3-05f0-9041-a586-fe7591c9154c@catalyst.net.nz

 · 

reply
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: mark.kirkwood@catalyst.net.nz, sfrost@snowman.net
  Subject: Re: Bad recovery: no pg_xlog/RECOVERYXLOG
  In-Reply-To: <c37a48d3-05f0-9041-a586-fe7591c9154c@catalyst.net.nz>

* 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