From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Galy Lee" <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Deadline-Based Vacuum Delay |
Date: | 2006-12-29 00:27:48 |
Message-ID: | c2d9e70e0612281627p67a5bebeu953905ba13a765af@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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)
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-12-29 02:34:05 | Re: TODO: GNU TLS |
Previous Message | Tom Lane | 2006-12-28 23:36:18 | Re: Strange pgsql crash on MacOSX |