From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
Cc: | Scot Kreienkamp <SKreien(at)la-z-boy(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: question about pg_dump |
Date: | 2009-10-22 23:33:56 |
Message-ID: | dcc563d10910221633p195a3486k85414dc8be2b7e55@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/10/22 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
>
>
> On Thu, Oct 22, 2009 at 3:42 PM, Scot Kreienkamp <SKreien(at)la-z-boy(dot)com>
> wrote:
>>
>> Hi everyone,
>>
>>
>>
>> I have a question about pg_dump backups. Will changes made in the
>> database made during a pg_dump operation be reflected in the dumped
>> datafile? Or is the data the exact dataset that was in the database as of
>> the start of the backup?
>
> pg_dump opens transaction, on a serializable isolation level. In short, it
> is the proper full isolation level (as oppose to the default one: "read
> committed"). It can cause locks up on database, but the idea is that the
> dump it self is a snapshot, and is fully atomic.
Only DDL type stuff should be locked. Regular updates / inserts /
delete should run just fine during a backup.
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-10-22 23:59:17 | Re: Problem calling C function in PostgreSQL |
Previous Message | Scott Marlowe | 2009-10-22 23:06:30 | Re: Right Join Question |