On 02/08/2006 09:46:46 PM, Tom Lane wrote:
"Karl O. Pinc" <kop@xxxxxxxx> writes:
> 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.)
What's wrong with SET?
For my purposes at the moment, probably nothing.
But isn't SET server wide? With autovacuum turned
on I wouldn't want other vacuums affected. I'd
want to give a single, important, vacuum process
"first class" status and relegate all the other
vacuums to the background where they belong.
(Especially if SET did not change the operation
of already running vacuum processes, something
I'm unclear on in my present foggy brain state.
(Are the docs clear?) Wouldn't want
to get bitten by an inopportune automatic vacuum
of a large table at the wrong time.)
Karl <kop@xxxxxxxx>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
