Re: Some thoughts about i/o priorities and throttling vacuum

From: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Some thoughts about i/o priorities and throttling vacuum
Date: 2003-10-17 14:31:05
Message-ID: 3F8FFD29.2080805@persistent.co.in
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> writes:
>
>>What part of plain vacuum takes disk bandwidth?
>
>
> Reading (and possibly rewriting) all the pages.

I was under impression that was for shared memory pages only and not for disk pages.

OK. I can see difference of understanding here.

Plain Vacuum goes around the table/database and makes space, shared buffers and
disks, reusable whenever possible but *does not* free any space.

Would it be possible to have a vacuum variant that would just shuffle thr.
shared buffers and not touch disk at all? pg_autovacuum could probably be ulra
agressive with such a shared-buffers only scan? Is it possible or feasible?

IMO that could be a clever solution rather than throttling IO for vacuum. For
one thing, getting that throttiling right, would be extremely difficult and
varying from site to site. If it is going to be tough to tune, then it will be
underutilised and will lose it's value rather rapidly.

Just a thought..

Shridhar

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2003-10-17 14:32:10 Re: Mapping Oracle types to PostgreSQL types
Previous Message Shridhar Daithankar 2003-10-17 14:25:44 Re: Some thoughts about i/o priorities and throttling vacuum