Re: Feedback on getting rid of VACUUM FULL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Feedback on getting rid of VACUUM FULL
Date
Msg-id 5317.1253157166@sss.pgh.pa.us
Whole thread Raw
In response to Re: Feedback on getting rid of VACUUM FULL  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Feedback on getting rid of VACUUM FULL
List pgsql-hackers
Jeff Davis <pgsql@j-davis.com> writes:
> On Wed, 2009-09-16 at 21:48 -0400, Tom Lane wrote:
>> Yeah, I was just wondering about that myself.  Seems like there would
>> be lots of situations where short exclusive-lock intervals could be
>> tolerated, even though not long ones.

> But a short-lived exclusive lock can turn into a long-lived exclusive
> lock if there are long-lived transactions ahead of it in the queue. We
> probably don't want to automate anything by default that acquires
> exclusive locks, even for a short time. However, I agree that it's fine
> in many situations if the administrator is choosing it.

Right, which is why autovacuum can't have anything to do with this.
But as an emergency recovery tool it seems reasonable enough.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Feedback on getting rid of VACUUM FULL
Next
From: Emmanuel Cecchet
Date:
Subject: Re: generic copy options