Re: PG_DUMP and table locking in PG7.4

From: Andrew - Supernews <andrew+nonews(at)supernews(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG_DUMP and table locking in PG7.4
Date: 2005-11-16 03:38:54
Message-ID: slrndnlaee.nb4.andrew+nonews@trinity.supernews.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2005-11-16, Yann Michel <yann-postgresql(at)spline(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-11-16 03:40:48 OS X 7.4 failure
Previous Message Yann Michel 2005-11-16 03:09:20 Re: PG_DUMP and table locking in PG7.4