Re: Pg_dump consistency.

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: samana srikanth <samanasrikanth(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Pg_dump consistency.
Date: 2009-05-06 09:48:51
Message-ID: dcc563d10905060248j72b3c57fh49c2ab1bd6564a85@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, May 6, 2009 at 3:37 AM, samana srikanth
<samanasrikanth(at)gmail(dot)com> wrote:
> Hi All
> I have a doubt.
> let's say i have 100 tables in a database DB.
> when i say "pg_dump -d DB"
> It dumps the tables one after another.
> my question is lets say we have dependent tables.
> and at the time of pg_dump, we are bombarding the database tables with lots
> of data (inserts).

pg_dump runs in a serialized transaction, so it will always take a
consistent backup. This will not be a problem.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Mike Williams 2009-05-06 12:12:31 pg_standby exit codes
Previous Message samana srikanth 2009-05-06 09:37:02 Pg_dump consistency.