On Feb 12, 2008, at 9:13 AM, Thomas Chille wrote:
vacuum_cost_delay = 200
vacuum_cost_page_hit = 6
vacuum_cost_limit = 100
Vacuum is going to take forever with those settings. I strongly
suggest you set them back to default. If you need to throttle vacuum,
try setting cost
On Tue, Feb 12, 2008 at 04:13:33PM +0100, Thomas Chille wrote:
> We are still using 8.1.4 because a database upgrade for us and our
> product is a hefty step wich involves a lot of customer databases. But
> if it could help we consider to upgrade to 8.1.11 or 8.3. What would u
> suggest?
Obviously
Thomas Chille wrote:
Hi!
Some of our clients databases are performing less good after a while.
We are using autovacuum to vacuuming and analyzing the tables.
After some analyzes by my own it looks like that the tables or table
indexes are not analyzed or vacuumed fully or correctly.
You mig
Thomas Chille wrote:
> My 1. question is,
> if the known bugfixes for autovacuum after release 8.1.4 addressing my
> depicted issues?
Not directly, but keep reading.
> We are still using 8.1.4 because a database upgrade for us and our
> product is a hefty step wich involves a lot of customer dat
Hi!
Some of our clients databases are performing less good after a while.
We are using autovacuum to vacuuming and analyzing the tables.
After some analyzes by my own it looks like that the tables or table
indexes are not analyzed or vacuumed fully or correctly.
A count(*) query takes multiple t
