From: | "Adam Lang" <aalang(at)rutgersinsurance(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: VACUUM and 24/7 database operation |
Date: | 2001-01-24 15:03:19 |
Message-ID: | 008801c08616$c95a1360$330a0a0a@6014cwpza006 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Any type of commerce or site that tracks user profiles... That's a LOT of
sites that would have a need for a enterprise level DB.
Remember, the goal is 5 nines uptime. :)
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Steve Wolfe" <steve(at)iboats(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, January 23, 2001 3:52 PM
Subject: Re: [GENERAL] Re: VACUUM and 24/7 database operation
> > 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.
>
> steve
>
From | Date | Subject | |
---|---|---|---|
Next Message | clemens schmuck | 2001-01-24 15:12:21 | groups a user belongs to |
Previous Message | fabrizio.ermini | 2001-01-24 15:00:35 | Re: pleasing the corporate-types. |