| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
| Cc: | <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: PITR Functional Design v2 for 7.5 |
| Date: | 2004-03-10 17:37:41 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D015@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The only way we can support file-level hot backup is in conjunction with
> PITR-style WAL log archiving. It is okay for the data area dump to be
> inconsistent, so long as your recovery process includes replay of WAL
> starting at some checkpoint before the filesystem dump started, and
> extending to some point after the filesystem dump finished. Replaying
> WAL will correct the inconsistencies.
And the "last checkpoint" info resides in pg_control, and not in pg_clog, no ?
So basically a PITR restore would need to adjust the pg_control file
after filesystem restore and before starting recovery. Maybe it can take that
info from the oldest available WAL ? The OP would only need to ensure,
that only such logs that need to be rolled forward are visible (in the
correct directory) to the recovery.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-03-10 17:49:10 | remove log_timestamp, log_pid and log_source_port GUC vars |
| Previous Message | Andreas Pflug | 2004-03-10 17:33:25 | Re: PITR Functional Design v2 for 7.5 |