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

From Josh Berkus
Subject Re: Feedback on getting rid of VACUUM FULL
Date
Msg-id 4AB1318A.6070803@agliodbs.com
Whole thread Raw
In response to Re: Feedback on getting rid of VACUUM FULL  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Feedback on getting rid of VACUUM FULL
List pgsql-hackers
On 9/16/09 11:20 AM, Kevin Grittner wrote:
> Josh Berkus <josh@agliodbs.com> wrote:
>  
>> a) To date, I have yet to hear a single person bring up an actual
>> real-life use-case where VACUUM FULL was desireable and REWRITE
>> would not be.
>  
> Would rewrite have handled this?:
>  
> http://archives.postgresql.org/pgsql-hackers/2009-09/msg01016.php

Ok, that sounds like a real use case.

However, given Heikki's post about FULL being an issue for Hot Standby,
I'm more inclined to provide a workaround ... for example, allowing
REWRITE to write to a designated tablespace, which would allow people to
use a portable drive or similar for the extra disk space.

-- 
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Feedback on getting rid of VACUUM FULL
Next
From: Hannu Krosing
Date:
Subject: Re: Feedback on getting rid of VACUUM FULL