From: Cott Lang <cott@internetstaff.com>
To: pgsql-hackers-pitr@postgresql.org
Subject: Re: Review of last summer's PITR patch
Date: Thu, 12 Feb 2004 17:48:20 -0700
Message-ID: <1076633300.4312.214.camel@blackbox> (raw)
In-Reply-To: <25856.1076553698@sss.pgh.pa.us>
References: <25856.1076553698@sss.pgh.pa.us>
On Wed, 2004-02-11 at 19:41, Tom Lane wrote:
> Anyway, I'm hoping to see some discussion of what to do next and what
> the PITR functionality ought to look like from a user's standpoint.
As previously discussed on general ...
* WAL files archived to a different location instead of recycling.
* The ability to force a WAL log switch to ensure all changes during the
backup are flushed to archived logs and copied.
* Ability to easily apply WAL logs to a standby database. I'd love be
able to take a hot backup of my production database, bring it up on
another computer and keep it a log or two behind production by
continually copying and applying logs to it.
* Although not PITR, on a related note, having the ability to do
incremental pg_dumps would be a huge boon for those relying on pg_dumps
for backups.
* Oracle 10g's Flashback feature is interesting. You can roll the
entire database back to a point in time with:
> flashback database to '3:00 pm';
I would have to say it's hardly critical. :)
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers-pitr@postgresql.org
Cc: cott@internetstaff.com
Subject: Re: Review of last summer's PITR patch
In-Reply-To: <1076633300.4312.214.camel@blackbox>
References: <25856.1076553698@sss.pgh.pa.us> <1076633300.4312.214.camel@blackbox>
* 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