Quick Links

Re: PG_DUMP and table locking in PG7.4

From:	Yann Michel <yann-postgresql(at)spline(dot)de>
To:	Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc:	Yann Michel <yann-postgresql(at)spline(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject:	Re: PG_DUMP and table locking in PG7.4
Date:	2005-11-16 03:09:20
Message-ID:	20051116030920.GA6014@zoom.spline.inf.fu-berlin.de
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

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

Re: PG_DUMP and table locking in PG7.4 at 2005-11-16 01:59:44 from Christopher Kings-Lynne

Responses

Re: PG_DUMP and table locking in PG7.4 at 2005-11-16 03:38:54 from Andrew - Supernews
Re: PG_DUMP and table locking in PG7.4 at 2005-11-16 05:25:43 from Christopher Kings-Lynne

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Andrew - Supernews	2005-11-16 03:38:54	Re: PG_DUMP and table locking in PG7.4
Previous Message	Douglas McNaught	2005-11-16 02:13:09	Re: bind variables, soft vs hard parse