| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Campbell, Lance" <lance(at)uiuc(dot)edu>, posgres support <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Enhancement request |
| Date: | 2007-12-01 20:30:29 |
| Message-ID: | 20071201123029.5776b3c5@jd-laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 30 Nov 2007 19:34:02 -0300
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Joshua D. Drake escribió:
>
> > Autovacuum is a great utility for many workloads but even with the
> > upcoming changes I will continually find myself turning off
> > autovacuum for specific relations just so I can turn around and
> > turn on vacuum within cron for others.
> >
> > The multi-worker autovacuum is a great new addition to help part of
> > that problem (starvation) but it is not help against the other
> > (resource consumption, specifically IO).
>
> Huh, autovac will consume exactly the same amount of I/O as a
> user-induced vacuum, so I don't see your point.
It can be determined "when" the I/O is used.
> Remember, we're not adding VACUUM SCHEMA in 8.2 so it doesn't make any
> sense to try to compare it against the old autovac. And you can bet
> that in 8.4 autovac will have even more goodies.
>
I assume you mean 8.3, but that is certainly a valid point.
Sincerely,
Joshua D. Drake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-12-02 01:31:14 | Re: Enhancement request |
| Previous Message | Tom Lane | 2007-12-01 03:44:18 | Re: Enhancement request |