Re: PG_DUMP and table locking in PG7.4 - Mailing list pgsql-hackers

From Andrew - Supernews
Subject Re: PG_DUMP and table locking in PG7.4
Date
Msg-id slrndnlaee.nb4.andrew+nonews@trinity.supernews.net
Whole thread Raw
In response to PG_DUMP and table locking in PG7.4  (Yann Michel <yann-postgresql@spline.de>)
List pgsql-hackers
On 2005-11-16, Yann Michel <yann-postgresql@spline.de> wrote:
> Hi,
>
> On Wed, Nov 16, 2005 at 09:59:44AM +0800, Christopher Kings-Lynne wrote:
>> It acquires share locks on EVERY table.
>
> do you mean on EVERY inherited table once one of them is dumped? Or do
> you mean that a share lock is requested(and hold) on each of them once
> one is dumped, i.e., sequentially?

pg_dump obtains an ACCESS SHARE lock on _every_ table it dumps, including
the inherited child tables individually, _before_ it starts dumping anything.

-- 
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services


pgsql-hackers by date:

Previous
From: Yann Michel
Date:
Subject: Re: PG_DUMP and table locking in PG7.4
Next
From: "Jim C. Nasby"
Date:
Subject: OS X 7.4 failure