Re: First steps with 8.3 and autovacuum launcher - Mailing list pgsql-hackers

From Tom Lane
Subject Re: First steps with 8.3 and autovacuum launcher
Date
Msg-id 23795.1191279220@sss.pgh.pa.us
Whole thread Raw
In response to Re: First steps with 8.3 and autovacuum launcher  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: First steps with 8.3 and autovacuum launcher
Re: First steps with 8.3 and autovacuum launcher
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> We should not allow VACUUM to be concurrent with either CREATE INDEX or
> ANALYZE, but then thats not the problem here anyway.

I can't believe anyone is short-sighted enough to think that.

The problem here is that autovac takes locks that block foreground
sessions that want exclusive locks.  We've always known this and always
ignored it, but if autovac is on by default then it's going to be in
people's faces a lot more than it was before, and they won't be happy.

If you insist on crafting a solution that only fixes this problem for
pg_restore's narrow usage, you'll be back revisiting it before beta1
has been out a month.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: First steps with 8.3 and autovacuum launcher
Next
From: Alvaro Herrera
Date:
Subject: Re: First steps with 8.3 and autovacuum launcher