| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Glen Parker <glenebob(at)nwlink(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem with Online-Backup |
| Date: | 2007-02-02 00:26:25 |
| Message-ID: | 1708.1170375985@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Glen Parker <glenebob(at)nwlink(dot)com> writes:
>> Tarring hot database files still gives me the willies. But then, I
>> wear belt and suspenders.
> I understand. A list of "file changed while we read it" errors is just
> a little unnerving at first!
> I did quite a few end to end backup/PITR tests, and no matter what I did
> to the DB during backup, no matter how many errors tar or cpio produced,
> I have been unable to find any problems with the end result.
In theory, at least, this is exactly as reliable as Postgres' crash
recovery: it's essentially the same mechanism that gets us back to a
consistent state on-disk after a crash. So don't worry too much about
all those gripes from tar. (The only real problem with 'em is they
might distract you from a more serious problem, like out-of-space.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Caduto | 2007-02-02 00:35:45 | Re: I "might" have found a bug on 8.2.1 win32 |
| Previous Message | Mark Walker | 2007-02-02 00:22:07 | Re: How to allow users to log on only from my application not from pgadmin |