We have a web application which has 15 tables. Out of these, 7 tables has >
400000 records. The client application automatically connects to Postgres
database (at server) after 1 1/2 hours and performs INCREMENTAL UPLOAD to
server from client.
Upload option works fine after VACUUM but after 3-4 days, it starts giving
ERRORs... Again, we have to run VACUUM to solve the prob..
So, now a days, it has become our routine to run VACUUM every day to avoid
ERRORs.. caz, when ERROR shown, it causes bad impression on client.
Is there any parameters setting in DATABASE or anything else we can do
(except VACUUM regularly) ?
Postgres 7.2 on Redhat Linux 7.2
In response to
- logging at 2002-09-25 00:33:19 from Devinder K Rajput
pgsql-novice by date
|Next:||From: Aarni Ruuhimäki / Megative Tmi / KYMI.com||Date: 2002-09-26 06:24:02|
|Subject: Re: Vacuum again and again|
|Previous:||From: Doug Silver||Date: 2002-09-25 17:38:24|
|Subject: Re: Setting primary key on existing table|