From: | Chris Hoover <revoohc(at)gmail(dot)com> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: What happens to transactions durring a pg_dump? |
Date: | 2006-01-09 18:00:07 |
Message-ID: | 1d219a6f0601091000u45439e1dq1eb8296e8ffa3dba@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 1/9/06, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
>
> On Mon, Jan 09, 2006 at 12:22:27PM -0500, Chris Hoover wrote:
> > I'm trying to understand better what happens to a transaction that is
> > commited in the middle of a pg_dump. Is the transaction included in the
> > database dump, or is it excluded.
>
> If you look at the pg_dump source code or turn on query logging,
> you should see that pg_dump starts with
>
> BEGIN
> SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
>
> See "Transaction Isolation" in the "Concurrency Control" chapter of the
> documentation for an explanation of what that means.
>
> http://www.postgresql.org/docs/8.1/interactive/transaction-iso.html
>
> --
> Michael Fuhr
>
Just to make sure I correctly understood what I read, once pg_dump issues
the :
BEGIN
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
The backup will only see transactions that were commited before the
isolation level was set Is this correct? Any transactions that are commited
while the backup is running are not seen by pg_dump.
Correct?
Thanks,
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-09 18:48:20 | Re: postgresql.conf |
Previous Message | Michael Fuhr | 2006-01-09 17:45:11 | Re: What happens to transactions durring a pg_dump? |