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 10262.1253197314@sss.pgh.pa.us
Whole thread Raw
In response to Re: Feedback on getting rid of VACUUM FULL  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: Feedback on getting rid of VACUUM FULL
Re: Feedback on getting rid of VACUUM FULL
Re: Feedback on getting rid of VACUUM FULL
List pgsql-hackers
Hannu Krosing <hannu@2ndQuadrant.com> writes:
> On Wed, 2009-09-16 at 21:19 -0400, Tom Lane wrote:
>> VACUUM FULL CONCURRENTLY is a contradiction in terms.  Wishing it were
>> possible doesn't make it so.

> It depends on what do you mean by "VACUUM FULL"

Anything that moves tuples is not acceptable as a hidden background
operation, because it will break applications that depend on CTID.

The utility Heikki is talking about is something that DBAs would
invoke explicitly, presumably with an understanding of the side effects.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: generic copy options
Next
From: Hannu Krosing
Date:
Subject: Re: Feedback on getting rid of VACUUM FULL