Re: New VACUUM FULL - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: New VACUUM FULL
Date
Msg-id 1261476646.7442.4139.camel@ebony
Whole thread Raw
In response to Re: New VACUUM FULL  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: New VACUUM FULL  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
On Tue, 2009-12-22 at 18:11 +0900, Takahiro Itagaki wrote:

> Instead, I'd suggest to have conditional database-wide maintenance
> commands, something like:
>     VACUUM FULL WHERE <the table is fragmented>
> 
> We don't have to support the feature by SQL syntax; it could be done
> in client tools.  How about pg_maintain or pg_ctl maintain that cleans
> up each relation with appropriate command? We could replace vacuumdb,
> clusterdb, and reindexdb with it then.

Some broad thoughts...

Our perception of acceptable change is much higher than most users. If
we tell people "use VACUUM FULL" or vacuumdb -f, then that command
should, if possible, continue to work well across many releases.
vacuumdb in most people's minds is the command you run to ease
maintenance and make everything right, rather than a specific set of
features.

We have "It just works" as a principle. I think the corollary of that is
that we should also have "It just continues to work the same way".

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Small typos in Hot Standby docs
Next
From: Takahiro Itagaki
Date:
Subject: Re: New VACUUM FULL