Re: PG_DUMP and table locking in PG7.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yann Michel <yann-postgresql(at)spline(dot)de>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG_DUMP and table locking in PG7.4
Date: 2005-11-16 15:07:24
Message-ID: 5773.1132153644@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Yann Michel <yann-postgresql(at)spline(dot)de> writes:
> Well, now that I'm thinking about, what you've written I think this is
> exactly the point. I think, that there is a VACUUM waiting for the dump
> to finish whereas the INSERTS are waiting for the VACUUM to finish.

Only if it's a VACUUM FULL ... plain VACUUM neither blocks INSERT nor is
blocked by pg_dump.

The short answer may be "don't use VACUUM FULL" (at least not for
routine automatic vacuums).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-11-16 15:22:53 Re: question about count(b) where b is a custom type
Previous Message Andrew Dunstan 2005-11-16 14:55:15 Re: OS X 7.4 failure