Re: PG_DUMP and table locking in PG7.4

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
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 05:25:43
Message-ID: 437AC2D7.7000500@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-11-16 05:27:29 Re: MERGE vs REPLACE
Previous Message Tom Lane 2005-11-16 04:53:11 Re: Long-time 7.4 contrib failure Mac OS X 10.3.8