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

From Christopher Kings-Lynne
Subject Re: PG_DUMP and table locking in PG7.4
Date
Msg-id 437AC2D7.7000500@familyhealth.com.au
Whole thread Raw
In response to Re: PG_DUMP and table locking in PG7.4  (Yann Michel <yann-postgresql@spline.de>)
Responses Re: PG_DUMP and table locking in PG7.4  (Yann Michel <yann-postgresql@spline.de>)
List pgsql-hackers
I belive a lock is acquired on every table including inherited children 
BEFORE doing ANY dumping.  To allow pg_dump to get a consistent dump 
snapshot.

Chris

Yann Michel 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?
> 
> Thanks,
> Yann



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Long-time 7.4 contrib failure Mac OS X 10.3.8
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: MERGE vs REPLACE