| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: PITR Functional Design v2 for 7.5 | 
| Date: | 2004-03-10 15:04:07 | 
| Message-ID: | 6549.1078931047@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> To clarify:
> I'd expect a cluster to be workable, if I
> - disable VACUUM until backup completed
> - issue CHECKPOINT
> - backup clog (CHECKPOINT and backup clog are the "backup checkpoint")
> - backup all datafiles (which include at least all completed transaction 
> data at checkpoint time)
> and then
> - restore datafiles and clog
> - bring up pgsql.
Why is that a useful approach?  You might as well shut down the
postmaster and do a cold filesystem backup, because you are depending on
the data files (including clog) not to change after the checkpoint.  You
cannot make such an assumption in a running database.
Preventing VACUUM does not help btw.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-10 15:21:16 | Re: optimizing impossible matches | 
| Previous Message | Merlin Moncure | 2004-03-10 15:00:55 | Re: Timing of 'SELECT 1' |