| From: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
|---|---|
| To: | Duane Currie <dcurrie(at)sandman(dot)acadiau(dot)ca> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Hot Backup Ability |
| Date: | 1999-06-30 00:46:21 |
| Message-ID: | Pine.BSF.4.10.9906292146050.12242-100000@scifair.acadiau.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 29 Jun 1999, Duane Currie wrote:
> Anyway, version 6.5 apparently supports hot backups by using MVCC
> to give a view of a consistent version of the database during a
> pg_dump (http://postgresql.nextpath.com/doxlist.html search for
'backup')
Hrm. Nothing pops out.
Just out of curiosity, I did a DUMP on the database while running a script
that ran a pile of updates. When I restored the database files, it was so
corrupted that I couldn't even run a select. vacuum just core dumped...
If I can just run pg_dump to back it up, how does this guarantee any sort
of referential integrity? Also during such a dump, it seems that things
block while waiting for a lock. This also happens during a pg_vacuum. I
thought that mvcc was supposed to stop this...
-Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-06-30 01:09:48 | Re: [HACKERS] Hot Backup Ability |
| Previous Message | Hiroshi Inoue | 1999-06-30 00:36:37 | RE: [HACKERS] 6.5.1 status |