From: Tom Lane <tgl@sss.pgh.pa.us>
To: David.Bear@asu.edu
Cc: pgsql-admin@postgresql.org
Subject: Re: PITR with rsync
Date: Mon, 06 Aug 2007 20:27:13 -0400
Message-ID: <5382.1186446433@sss.pgh.pa.us> (raw)
In-Reply-To: <20070807001114.GD19294@asu.edu>
References: <20070807001114.GD19294@asu.edu>
David Bear <David.Bear@asu.edu> writes:
> I'm still uncomfortable with using the file system style backup method
> in PITR and am very interested in ' more information ' on how others
> may be doing backups. Specifically, I assume that PITR methods would
> also be accompanied with some combination of pg-dump.
You assume wrong. Replaying WAL demands starting from a physical not
logical dump, because page and tuple numbers and so forth have to be the
same as in the master. A pg_dump backup will simply not work.
> I am curious
> about how frequently a pg-dump would be done if a PITR method was also
> used (every 24 hours, every 7 days, not at all ) ??
I'd personally be inclined to take a pg_dump every now and then just to
have an independent backup method. Especially if I wasn't comfortable
with PITR ;-). How often depends on how much bandwidth you can spare
for backup purposes.
> Also, looking at the archive_command argument in postgresql.conf. Has
> anyone use rsync there?
I suppose you could, but what's the point? Copying a single file that
doesn't currently exist on the destination plays to none of rsync's
strengths.
regards, tom lane
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: tgl@sss.pgh.pa.us, David.Bear@asu.edu
Subject: Re: PITR with rsync
In-Reply-To: <5382.1186446433@sss.pgh.pa.us>
* 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