From: Usama Dar <munir.usama@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Campbell, Lance <lance@uiuc.edu>
Cc: posgres support <pgsql-admin@postgresql.org>
Subject: Re: Enhancement request
Date: Mon, 3 Dec 2007 01:51:23 +0500
Message-ID: <ff0e67090712021251x9745a37o230a9da22a1dca33@mail.gmail.com> (raw)
In-Reply-To: <20071202013114.GB11039@alvh.no-ip.org>
References: <B10E6810AC2A2F4EA7550D072CDE8760197E2C@SAB-FENWICK.sab.uiuc.edu>
<36e682920711301218m703b3c67s6f547fd7b9b60e7c@mail.gmail.com>
<7099.1196458205@sss.pgh.pa.us>
<36e682920711301332q1cce5db9qe44fb068fcd5608d@mail.gmail.com>
<7341.1196459304@sss.pgh.pa.us>
<20071130140005.18521c54@jd-laptop>
<20071130223402.GG3175@alvh.no-ip.org>
<20071201123029.5776b3c5@jd-laptop>
<20071202013114.GB11039@alvh.no-ip.org>
On Dec 2, 2007 6:31 AM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Joshua D. Drake escribió:
> > On Fri, 30 Nov 2007 19:34:02 -0300
> > Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> >
> > > Joshua D. Drake escribió:
> > >
> > > > 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.
>
> Future plans call for being able to change autovac parameters depending
> on time of day, so you will be able to decide that using autovacuum too.
>
> > > 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.
>
> No, I meant 8.4 --- the feature set of 8.3 is already set on stone. So
> VACUUM SCHEMA has to compete with whatever we're able to do for the
> release following that one.
i think even when autovacuum is uber-perfect , the manual overriding
commands like VACUUM and utilities like VACUUMDB will still exist for a long
time to come, so there is a case of improving them if required. Maybe it
would be just easier to add a schema switch to VACUUMDB, which can just
query the catalogs to find which tables to vacuum, this way no parser
changes are involved or any tinkering with the backend code.
>
> --
> Alvaro Herrera
> http://www.advogato.org/person/alvherre
> "Entristecido, Wutra (canción de Las Barreras)
> echa a Freyr a rodar
> y a nosotros al mar"
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
--
Usama Munir Dar http://linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: munir.usama@gmail.com, alvherre@alvh.no-ip.org, jd@commandprompt.com, tgl@sss.pgh.pa.us, jonah.harris@gmail.com, lance@uiuc.edu
Subject: Re: Enhancement request
In-Reply-To: <ff0e67090712021251x9745a37o230a9da22a1dca33@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox