Re: autovacuum next steps, take 3

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
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>, alvherre(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: autovacuum next steps, take 3
Date: 2007-03-13 04:25:22
Message-ID: 20070313131134.608E.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Who said anything about external schedulers? I remind you that this is
> AUTOvacuum. If you want to implement manual scheduling you can still
> use plain 'ol vacuum commands.

I think we can split autovacuum into two (or more?) functions:
task gatherers and task workers. We don't have to bother with
the monolithic style of current autovacuum.

Galy said:
> The task queue might be filled by dedicated task-gathering-worker or it
> might be filled by *external task gatherer*.

Alvaro said:
> The idea of an external task gatherer is an interesting one which I
> think would make sense to implement in the future. I think it is not
> very difficult to implement once the proposal we're currently discussing
> is done

I said:
> Though we can use a completely separated autovacuum daemon like as
> contrib/pg_autovacuum of 8.0, but I think it is good for us to share
> some of the codes between a built-in scheduler and external ones.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ITAGAKI Takahiro 2007-03-13 04:40:42 Re: Bug: Buffer cache is not scan resistant
Previous Message Tom Lane 2007-03-13 03:59:54 Re: autovacuum next steps, take 3