Re: incremental backups

From: Rick Gigger <rick(at)alpinenetworking(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Richard Huxton <dev(at)archonet(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: incremental backups
Date: 2006-01-31 16:09:31
Message-ID: B41FD9DE-C1F7-4080-B4D1-A01A50864F1C@alpinenetworking.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Wonderful. That is good news. Thanks.

Rick

On Jan 31, 2006, at 7:14 AM, Tom Lane wrote:

> Rick Gigger <rick(at)alpinenetworking(dot)com> writes:
>> That's what I mean by invalid. Let's say I do something stupid and
>> do a physical backup and I don't grab the current WAL file. All I
>> have is the last one to be archived before I did my backup, which is
>> not late enough to do a valid restore. Will postgres know that the
>> restore process failed because I didn't have that last necessary WAL
>> file or will it just start up in a potentially inconsistent state.
>
> Yes:
>
> /*
> * Complain if we did not roll forward far enough to render the
> backup
> * dump consistent.
> */
> if (XLByteLT(EndOfLog, recoveryMinXlogOffset))
> {
> if (needNewTimeLine) /* stopped because of stop request */
> ereport(FATAL,
> (errmsg("requested recovery stop point is
> before end time of backup dump")));
> else
> /* ran off end of WAL */
> ereport(FATAL,
> (errmsg("WAL ends before end time of backup
> dump")));
> }
>
> regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dave Page 2006-01-31 16:22:26 Re: Automatic monitoring
Previous Message Henrique Engelmann 2006-01-31 16:06:19 Automatic monitoring