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

From Tom Lane
Subject Re: PG_DUMP and table locking in PG7.4
Date
Msg-id 5773.1132153644@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG_DUMP and table locking in PG7.4  (Yann Michel <yann-postgresql@spline.de>)
Responses Re: PG_DUMP and table locking in PG7.4  (Yann Michel <yann-postgresql@spline.de>)
List pgsql-hackers
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).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: OS X 7.4 failure
Next
From: Tom Lane
Date:
Subject: Re: question about count(b) where b is a custom type