Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_basebackup problem... - Mailing list pgsql-admin

From John Scalia
Subject Re: pg_basebackup problem...
Date
Msg-id CABzCKRDerRQKT4B17=QPAy3QXuX0ZabZ9ss+uXuuSQQy7YGYog@mail.gmail.com
Whole thread Raw
In response to Re: pg_basebackup problem...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-admin
Tree view
Well, all is good now, I followed the instructions for pg_resetxlog and one of the most recent backups generated without fetching the WAL files in pg_xlog, did successfully start up after the procedure.

Everybody affected here is now in a far happier mood as a result. Thanks to everyone on this list, and especially to Kevin for reminding of pg_resetxlog.
--
Jay

On Thu, Aug 6, 2015 at 3:15 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
On 8/6/15 12:49 PM, Kevin Grittner wrote:
>> 2) If a WAL segment is in fact required for the backed up DB to
>> > start, why would pg_basebackup not include those by default? To
>> > not do so, doesn't create a backup file, just in this case, a
>> > tarball that's worthless.
> ... unless you are archiving the WAL to somewhere that it will be
> kept long enough to be usable for such purposes.  If you are (and I
> highly recommend that you do so), including WAL in the base backup
> is a waste of both bandwidth and storage space.

This is arguably an artifact of the evolution of replication in
PostgreSQL.  You used to do tar backup + archiving, then you could
switch to pg_basebackup + archiving, and nowadays you could switch to
pg_basebackup without archiving, but the default behavior of
pg_basebackup still caters to the old case.


pgsql-admin by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup problem...
Next
From: HEMPLEMAN Matthew
Date:
Subject: Replication Cluster Monitoring