From: Thomas Karcher <thkarcher@gmx.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Consistent PITR backup
Date: Thu, 11 Oct 2007 16:37:05 +0200
Message-ID: <1192113425.9842.2.camel@localhost.localdomain> (raw)
In-Reply-To: <13019.1192112569@sss.pgh.pa.us>
References: <20071011093908.GA7988@arche.mine.nu>
<13019.1192112569@sss.pgh.pa.us>
Hi Tom,
> > My idea is now: When doing a consistent PITR backup, extend the
> > documented steps between 4 (pg_stop_backup()) and 5 (wait for archived
> > WAL file) with a busy wait on pg_xlog/archive_status/*.ready files - as
> > soon as no .ready files are there anymore, the archiver has done its
> > work, and I can safely backup the archived WAL files in order to have a
> > really consistent backup.
> If the database is busy, you might never see an instant where there are
> no .ready files. Certainly it's possible that this approach will
> archive many more segments than you need.
I see - but the risk for never seeing an instant without .ready files is
relatively slow, I hope. And compared to the risk of not having a
consistent backup, I could live with having backed up more WAL files
than I actually would have needed.
> > Is that right? Or is there an easier way to do it?
> I believe the intended way to do this is to look at pg_stop_backup's
> return value to determine the last segment you need to archive.
Thank you - I saw that, but I didn't have a clue about how to determine
the WAL filename in which this segment is to be found ...
Thank you & regards,
Thomas
Attachments:
signature.asc (application/pgp-signature, 188B) download
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: thkarcher@gmx.de, tgl@sss.pgh.pa.us
Subject: Re: Consistent PITR backup
In-Reply-To: <1192113425.9842.2.camel@localhost.localdomain>
* 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