From: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
---|---|
To: | Steve Wolfe <steve(at)iboats(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: VACUUM and 24/7 database operation |
Date: | 2001-01-23 23:01:26 |
Message-ID: | 20010123150125.G26076@fw.wintelcom.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Steve Wolfe <steve(at)iboats(dot)com> [010123 13:11] wrote:
> > Shouldn't it be possible to build vacuum as an ongoing internal PG
> process,
> > instead of a seperate operation? How does Oracle byepass this? Must be
> some
> > way that can be implemented.
>
> Well, here's what it comes down to: Do you want updates to happen
> quickly, and vacuum when load is low, or do you want updates to be slow all
> the time? I suppose that there are some sites that can't find two minutes
> per day when updates will block (not selects), but I imagine they're very
> few.
There are some sites where going for more than an hour without a
VACUUM makes response times unnaceptable, and each vacuum can take
20 minutes a run.
Yes, I'm _an_ exception, but I know I'm not the only one out there.
--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."
From | Date | Subject | |
---|---|---|---|
Next Message | <No Name> | 2001-01-23 23:05:42 | Re: GUI admin interface - where?? |
Previous Message | Tom Lane | 2001-01-23 22:52:18 | Re: VACUUM ANALYZE FAILS on 7.0.3 |