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 01:59:44 |
Message-ID: | 437A9290.20007@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It acquires share locks on EVERY table.
Yann Michel wrote:
> Hi all,
>
> On Sun, Nov 13, 2005 at 03:22:23AM +0100, Yann Michel wrote:
>
>>I'm using PG_DUMP for backing up a postgres 7.4 database. As I have
>>seen, the pg_dump aquires a table lock while dump the table's content.
>>What will happen, if I have a basic table and several inherited tables.
>>Will the PG_DUMP tool only aquire locks on the inherited tables or on
>>the parent-table, too?
>
>
> Is anyone out there who could answer this question or even give me a
> hint about where to read about this if there is any writen things about
> that?
>
> Thanks!
>
> Yann
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Douglas McNaught | 2005-11-16 02:13:09 | Re: bind variables, soft vs hard parse |
Previous Message | Christopher Kings-Lynne | 2005-11-16 01:51:41 | Re: Réf. : Re: [HACKERS] Runn |