vacuum

From: "Dr R(dot)Adscheid" <Reinhold(dot)Adscheid(at)rosin(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: vacuum
Date: 2001-01-25 09:38:24
Message-ID: 94os98$2ui2$1@news.tht.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We are using PostgreSQL 6.3 in an environment with 7x24 availiability. There
is one table, which has about 9000 new records per day and about 10% beeing
updated. With an index over several columns the select on this table is quit
short, but when removing old entries and vacuuming, this is an very time
consuming operation (about 1 hour for the whole database!) and because of
the 7x24 production not acceptable. On the other hand, no index improves the
removing and vacuuming, but now the select is very time consuming, which is
also not acceptable. Even with the best solution (some index, which improves
the select but slows down the cleaning) our customer complaints .

The best way to solve this, would be to remove the feature of keeping
deleted/updated records in the databasefiles and therefor no need to vacuum.
Is there any way to configure this when compiling? Or are there other
possibilities?

Browse pgsql-general by date

  From Date Subject
Next Message Robert B. Easter 2001-01-25 09:49:56 Re: database transfer
Previous Message Peter T Mount 2001-01-25 09:26:03 Re: [GENERAL] jdbc driver, error trapping.