Heikki Linnakangas wrote:
> So I guess what I'm asking is: Does anyone see any show-stoppers in
> removing VACUUM FULL
Here's the disclaimers attached to the new VACUUM REPLACE implementation
from Itagaki:
"We still need traditional VACUUM FULL behavior for system catalog
because we cannot change relfilenode for them. Also, VACUUM FULL REPLACE
is not always better than traditional VACUUM FULL; the new version
requires additional disk space and might be slower if we have a few dead
tuples."
That first part seems like it would limit the ability to completely
discard the current behavior.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.com