Re: Problem with PITR recovery

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ragnar Hafstað <gnari(at)simnet(dot)is>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem with PITR recovery
Date: 2005-04-18 22:38:52
Message-ID: 1113863932.16721.2055.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2005-04-18 at 13:41 -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > I guess I didn't see the connection between the file system backup and
> > > the WAL files, when in fact you need the WAL files that go with the file
> > > system badckup to do the recovery. Do you have new suggested text?
> >
> > I think it probably needs to mention *both* the tar dump and the WAL
> > segment file(s). I can take a whack at it if you like.
>
> I modified the sentence to say:
>
> Once you have safely archived the file system backup and the WAL segment
> files used during the backup (as specified in the backup history file),
> you can delete all archived WAL segments with names numerically less.
>
> Feel free to whack it a second time.

whack...

...you can delete all archived WAL segments with names numerically
less.

but I'm not sure it's best practice to delete them at that point. I
would recommend that users keep at least the last 3 backups. So, I'd
prefer the wording

...all archived WAL segments with names numerically less will no longer
be needed as part of that backup set. You may delete them at that point,
though you should consider keeping more than one backup set to be
absolutely certain that you are can recover your data.

Best Regards, Simon Riggs

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-04-18 22:56:34 Re: argtype_inherit() is dead code
Previous Message Simon Riggs 2005-04-18 22:20:23 Re: Problem with PITR recovery