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

From Yann Michel
Subject Re: PG_DUMP and table locking in PG7.4
Date
Msg-id 20051116204325.GB22667@zoom.spline.inf.fu-berlin.de
Whole thread Raw
In response to Re: PG_DUMP and table locking in PG7.4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PG_DUMP and table locking in PG7.4  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Hi,

On Wed, Nov 16, 2005 at 10:07:24AM -0500, Tom Lane wrote:
> Yann Michel <yann-postgresql@spline.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).

... I guiess that the AUTOVACUUM switch only does an automated VACUUM
but no VACUUM FULL?


Cheers,
Yann


pgsql-hackers by date:

Previous
From: Yann Michel
Date:
Subject: Re: PG_DUMP and table locking in PG7.4
Next
From: Greg Stark
Date:
Subject: Re: Some array semantics issues