From: Peter Eisentraut <peter_e@gmx.net>
To: Kevin Grittner <kgrittn@ymail.com>
To: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_basebackup problem...
Date: Thu, 06 Aug 2015 16:15:47 -0400
Message-ID: <55C3C073.4000207@gmx.net> (raw)
In-Reply-To: <2095928829.121339.1438879776368.JavaMail.yahoo@mail.yahoo.com>
References: <CABzCKRBUsSw+B3kQa8RCKx3D_LMg=A4hUS05=L5hamFP01BJgA@mail.gmail.com>
<2095928829.121339.1438879776368.JavaMail.yahoo@mail.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: peter_e@gmx.net, kgrittn@ymail.com, jayknowsunix@gmail.com
Subject: Re: pg_basebackup problem...
In-Reply-To: <55C3C073.4000207@gmx.net>
* 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