| From: | Mike Mascari <mascarm(at)mascari(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Some thoughts about i/o priorities and throttling vacuum |
| Date: | 2003-10-17 18:56:48 |
| Message-ID: | 3F903B70.1040001@mascari.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> Christopher Browne <cbbrowne(at)libertyrms(dot)info> writes:
>
>>VACUUM is like putting an extra few transport trucks onto the highway.
>>It may only go from one highway junction to the next, and be fairly
>>brief, if traffic is moving well. But if traffic is heavy, it adds to
>>the congestion. (And that's as far as the analogy can go; I can't
>>imagine a way of drawing the GUC parameter into this...)
>
> Ooh strained metaphors. This game is always fun.
>
> So I think of it the other way around. A busy database is like downtown
> traffic with everyone going every which way for short trips. Running vacuum is
> like having a few trucks driving through your city streets for through
> traffic.
>
> Having a parameter to slow down the through traffic is like, uh, having
> express lanes for local traffic. er, yeah, that's the ticket. Except who ever
> heard of having express lanes for local traffic. Hm.
All I know is that Jan Wieck would have each car filled to the brim
with spikes....
Mike Mascari
mascarm(at)mascari(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2003-10-17 20:22:53 | Vacuum thoughts |
| Previous Message | Greg Stark | 2003-10-17 18:47:28 | Re: Some thoughts about i/o priorities and throttling vacuum |