Well, all you're doing with pg_dump is getting a snapshot of the database at
a single point in time -- as pg_dump reads the data out of the tables, I'm
sure that it won't go back and re-read tables that have changed since it was
first started. On the other hand, if pg_dump is busy on table A and table Z
changes, even though it's after the pg_dump process starts, I would assume
the changes to table Z would get dumped.
I'm assuming a lot -- all of that is based on the fact that I've never seen
pg_dump lock the whole database down (though I do think it locks the table
it's dumping while it's dumping it)..
-Mitch
----- Original Message -----
From: "Vilson farias" <vilson.farias@digitro.com.br>
To: <pgsql-general@postgresql.org>
Cc: "SIMONE Carla MOSENA" <simone.mosena@digitro.com.br>
Sent: Friday, October 13, 2000 11:53 AM
Subject: [GENERAL] Question about pg_dump
> Hi.
>
> I started testing pg_dump and I have a little question :
>
> What does pg_dump with data arrived while its running?
>
> Lets suppose I'd started a pg_dump mybase > /home/postgres/text.txt and
> while its running, new data was inserted into its tables.
>
> All data that cames after the beginning of processing are ignored ? How
can
> I deal with it?
>
>
> José Vilson de Mello de Farias
> Dígitro Tecnologia ltda - Brazil
>
>
