| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 15:40:34 |
| Message-ID: | 7419.1010590834@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Jean-Christophe ARNU <jc(dot)arnu(at)free(dot)fr> writes:
> 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.
?? 7.2 is not out yet. Did you mean 7.1.2? Or are you running a beta
release of 7.2?
> 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)?
7.2 can run vacuum in parallel with regular queries.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | solar2000 | 2002-01-09 16:07:23 | help with recovery of deleted table |
| Previous Message | Manuel Trujillo | 2002-01-09 15:23:19 | Re: dumping users objects |