> I think the new VACUUM is a great thing, and frankly I don't care all
> that much about the VACUUM FULL command issue. I tend to take the view
> that command semantics shouldn't be changed if one can avoid it. It's a
> view built on the fact that about twenty years of my past life were
> spent as a language implementor and dealing with customer feedback when
> I've been foolish enough to make semantics changes of this sort.
I actually just add 'vacuumdb -a -z -q' sort of thing to my crontab. Which
version of VACCUM will vacuumdb be using in 7.2? Will there be an option to
vacuumdb to run VACUUM FULL if it defaults to just VACUUM?
In response to
pgsql-hackers by date
|Next:||From: Christopher Kings-Lynne||Date: 2001-12-19 02:45:55|
|Subject: Re: Explicit config patch 7.2B4|
|Previous:||From: Christopher Kings-Lynne||Date: 2001-12-19 02:24:33|
|Subject: Re: Concerns about this release |