From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Yann Michel <yann-postgresql(at)spline(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PG_DUMP and table locking in PG7.4 |
Date: | 2005-11-16 01:11:21 |
Message-ID: | 20051116011121.GB9402@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yann Michel wrote:
> Hi all,
>
> On Sun, Nov 13, 2005 at 03:22:23AM +0100, Yann Michel wrote:
> >
> > I'm using PG_DUMP for backing up a postgres 7.4 database. As I have
> > seen, the pg_dump aquires a table lock while dump the table's content.
> > What will happen, if I have a basic table and several inherited tables.
> > Will the PG_DUMP tool only aquire locks on the inherited tables or on
> > the parent-table, too?
>
> Is anyone out there who could answer this question or even give me a
> hint about where to read about this if there is any writen things about
> that?
You could find out exactly which commands it sends by setting
log_statement=all in a test environment and then dumping things to your
heart's content. Looking at that output you should be able to easily
determine which tables are locked.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-11-16 01:27:43 | Re: [ADMIN] Major Problem, need help! Can't run our website! |
Previous Message | Tatsuo Ishii | 2005-11-16 01:08:15 | Bug or feature? |