pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: gparc@free.fr
To: Campbell, Lance <lance@illinois.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Clarification on pg_basebackup
Date: Wed, 24 Sep 2014 09:42:22 +0200
Message-ID: <1411544542.542275de20713@imp.free.fr> (raw)
In-Reply-To: <B75CD08C73BD3543B97E4EF3964B7D701FBB7279@CITESMBX1.ad.uillinois.edu>
References: <B75CD08C73BD3543B97E4EF3964B7D701FBB7279@CITESMBX1.ad.uillinois.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Selon "Campbell, Lance" <lance@illinois.edu>:

 PostgreSQL 9.3
 Would someone be able to clarify if one should use the -X option with
 pg_basebackup when your intention is to include all WAL files created?  There
 are two scenarios.  The first scenario listed below makes sense using the -X
 option.  Bus scenario #2 has me a little confused.  I don't want to cause any
 issues when restoring.


 1)      Use pg_basebackup for a fully standalone restorable snapshot of the
 database using the -X parameter.  When a failure occurs you restore the
 database to that exact point in time.

 2)      You restore from a pg_basebackup and you also apply all of the WAL
 files since the last pg_basebackup.  Do you want to use the -X option when
 doing the pg_basebackup if your intention is to have all of the WAL files
 since you backed up last?  Or does it matter.  Would PostgreSQL just ignore
 the duplicate WAL files that were created by the -X option during the
 pg_basebackup?

 Thanks for your clarification.  This is a hard scenario to test.

 Thanks,

 Lance Campbell<http://illinois.edu/person/lance;
 Software Architect
 Web Services at Public Affairs
 217-333-0382
 [University of Illinois at Urbana-Champaign logo]<http://illinois.edu/;


For security, I will do both i.e pg_basebackup -X + continuous WAL archiving.
Reason : you never know what could happen with your WAL archiving process.
At least with -X you will have a "restartable" backup.


Regards

Gilles





-- 
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 (7+ messages)

Message-ID: <1411544542.542275de20713@imp.free.fr>
Permalink:  ../1411544542.542275de20713@imp.free.fr/
Also on:    postgresql.org/message-id/1411544542.542275de20713@imp.free.fr

 · 

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: gparc@free.fr, lance@illinois.edu
  Subject: Re: Clarification on pg_basebackup
  In-Reply-To: <1411544542.542275de20713@imp.free.fr>

* 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