| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Jean-Christophe ARNU <jc(dot)arnu(at)free(dot)fr> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Vaccum and 24/7/365 database |
| Date: | 2002-01-09 16:16:24 |
| Message-ID: | 20020109080954.F71288-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 9 Jan 2002, Jean-Christophe ARNU wrote:
> Hi all,
> we use postgresql 7.2 for a data logging/supervisor application running
> 24 hours a day, 7 days a week and 365 (and 6 hours) a year. Data are
> inserted/deleted/updated each 1,5 minutes and for performance reason we
> have to vacuum each day some tables. The problem is that vacuum stops
> inserts, updates and deletes for the table it performs (well in fact, I
> understood this). This way of working for the database does not fit our
> needs of 24/7/365 availability. So my question is : is there a way to
> get all the things work together (good performances & availability)?
AFAIK, if you're using a recent 7.2, the default VACUUM shouldn't prevent
inserts/updates/deletes from the table while the vacuum is occuring.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-01-09 16:19:22 | Re: Vaccum and 24/7/365 database |
| Previous Message | solar2000 | 2002-01-09 16:07:23 | help with recovery of deleted table |