From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Point in Time Recovery |
Date: | 2004-07-13 21:19:56 |
Message-ID: | 18739.1089753596@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> I'm getting carried away with the improbable....but this is the rather
> strange, but possible scenario I foresee:
> A sequence of times...
> 1. We start archiving xlogs
> 2. We take a checkpoint
> 3. we commit an important transaction
> 4. We take a backup
> 5. We take a checkpoint
> When we specify a recovery target, it is possible to specify the
> rollforward to complete just before point 3.
No, it isn't possible. The recovery *must* proceed at least as far as
wherever the end of the log was at the time the backup was completed.
Otherwise everything is broken, not only clog, because you may have disk
blocks in your backup that postdate where you stopped log replay.
To have a consistent recovery at all, you must replay the log starting
from a checkpoint before the backup began and extending to the time that
the backup finished. You only get to decide where to stop after that
point.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2004-07-13 22:25:34 | Re: Point in Time Recovery |
Previous Message | Simon Riggs | 2004-07-13 20:25:50 | Re: Point in Time Recovery |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-07-13 21:24:55 | Re: serverlog rotation/functions |
Previous Message | Bruce Momjian | 2004-07-13 21:19:06 | Re: Release planning (was: Re: Status report) |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-07-13 21:24:55 | Re: serverlog rotation/functions |
Previous Message | Bruce Momjian | 2004-07-13 21:17:19 | Re: pgsql-server: Have \dn+ show permissions and description |