Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Hot Backup Ability

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Michael Richards <miker(at)scifair(dot)acadiau(dot)ca>
Cc: Duane Currie <dcurrie(at)sandman(dot)acadiau(dot)ca>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Hot Backup Ability
Date: 1999-06-30 01:09:48
Message-ID: 199906300109.VAA03977@candle.pha.pa.us (view raw or flat)
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...

When you say DUMP, you mean pg_dump, right?  Are you using 6.5?

> 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...

OK, sounds like you are using pg_dump, and 6.5.  pg_vacuum still blocks,
but pg_dump shouldn't.  This sounds unusual.  You should have gotten
everything at the time of the _start_ of the dump.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Mike EmbryDate: 1999-06-30 01:18:54
Subject: Re: [HACKERS] User requests now that 6.5 is out
Previous:From: Michael RichardsDate: 1999-06-30 00:46:21
Subject: Re: [HACKERS] Hot Backup Ability

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group