Thread: Vaccum and 24/7/365 database
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)?
Thanks a lot.
--
Jean-Christophe ARNU
s/w developer
Paratronic France
Jean-Christophe ARNU <jc.arnu@free.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
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.
Jean-Christophe ARNU 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. 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 As of 7.2, this is no longer true. I recommend you read section 8.2 of the Administrator's Guide. -- Peter Eisentraut peter_e@gmx.net
> >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. Could someone please point me at a document explaining how to migrate from 7.1 to 7.2? -- Naomi Walker Chief Information Officer Eldorado Computing, Inc. 602-604-3100 ext 242