From: Scott Whitney <swhitney@journyx.com>
To: pgsql-admin@postgresql.org
Subject: PITR question with base backup
Date: Tue, 21 Oct 2008 15:02:39 -0500
Message-ID: <20081021200239.592B47E42AE@mail.int.journyx.com> (raw)
I'm in the process of testing PITR recovery, and I have an issue.
My "data" directory is 30GB. Not huge, but it certainly takes awhile to tar
up.
My understanding is:
a) pg_start_backup
b) tar up
c) pg_stop_backup
d) restore tar file
The problem is that I create databases pretty regularly. Let's say I create
3 in a week. I'm not looking forward to going to my colo, grabbing the 20ish
GB tgz file and restoring it 3 times per week. I'd rather do that dance
monthly or quarterly and rely on the WALs in the interim.
So...can I:
a) pg_start_backup
b) tar up my data dir
c) pg_stop_backup
d) restore
e) WALs are all happy
f) Day 2 - create new db
g) pg_start_backup
h) JUST grab the data/base directory for the new db
i) pg_stop_backup
move on?
What about "global" or "pg_clog" or "pg_multixact" or "pg_tblspc" and
"pg_twophase?"
I don't _think_ I would ever want clog, but maybe I'm wrong.
Is this possible, or do I absolutely need an entire new backup of the whole
data dir?
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: swhitney@journyx.com
Subject: Re: PITR question with base backup
In-Reply-To: <20081021200239.592B47E42AE@mail.int.journyx.com>
* 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