Re: Deadline-Based Vacuum Delay

On 12/29/06, Chris Browne <cbbrowne(at)acm(dot)org> wrote:
> systemguards(at)gmail(dot)com ("Jaime Casanova") writes:
> > On 12/28/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Galy Lee <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp> writes:
> >> > So I am thinking another way to perform vacuum. For example vacuum can
> >> > be refined in a maintenance time frame like "VACUUM IN 6 HOURS", and
> >> > then vacuum operation will be performed within the window. The delay
> >> > time is adjusted internally to spread the disk I/O over the time frame.
> >>
> >> And you will manage that how? The total amount of work to be done is
> >> quite unpredictable.
> >
> > specially for something you already can do with cron (*nix) or job
> > scheduler (windows)
>
> That seems like a nonsequitor here...
>
> Using cron to try to "make vacuums spread over 6 hours" seems to me
> like an attempt to try to do that in as terrible a way possible.
>

that's entirely my point... what th op was proposing was a command
"VACUUM IN n HOURS"... he want to write the command... he didn't talk
about a tool for monitoring jus a tool that he "fire and forget"... at
least that was the way a read it...

--
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook