Hi,
Just had a situation where a database was reloaded and needed to
be vacuum analyzed before it could be used. I believe the
cost-based vacuum delay slowed this down considerably.
(I could be wrong, but there was darn little load on the
system...)
It would have been nice to have an option to SQL's VACUUM that would
ignore the cost-based delays so as to bring that database back
to life as rapidly as possible. (Likewise the vacuumdb shell
command.)
Regards,
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
P.S. Thought I'd post here rather than to the deveoper's
list to get some general feedback.
