Re: pg_dumpall

From: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Steve Clark <sclark(at)netwolves(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dumpall
Date: 2008-01-17 19:14:22
Message-ID: 235223.76121.qm@web25809.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


>Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Glyn Astill wrote:
> > Out of interest, how does pg_dump manage to do a snapshot of a
> > database at an instant in time?
> >
> > My mental picture of pg_dump was just a series of queries dumping
> out
> > the tables...
>
> begin;
> set transaction isolation level serializable;
>
> --- begin dumping stuff;
>

Wouldn't that just lock everything so nothing could be updated? Or
just the table it is outputting?

I'm guessing I need to go off and school myself on different
isolation levels etc to understand, but say I have 2 tables "sales"
and "sold", and users are selling items with inserts into the sales
table and a count updating manually in sold. Wouldn't these end up
inconsistant in the dump?

___________________________________________________________
Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2008-01-17 19:21:35 Re: pg_dumpall
Previous Message Greg Smith 2008-01-17 19:08:07 Re: pg_dumpall