Ralph Mason wrote:
We have a database running on a 4 processor machine. As time goes by
the IO gets worse and worse peeking at about 200% as the machine loads up.
The weird thing is that if we restart postgres it’s fine for hours but
over time it goes bad again.
(CPU usage graph here
http://www.flickr.com/photos/[EMAIL PROTECTED]/502596262/ ) You can clearly
see where the restart happens in the IO area
This is Postgres 8.1.4 64bit.
1. Upgrade to 8.1.9. There is a bug with autovac that is fixed that is
pretty important.
Anyone have any ideas?
Sure... you aren't analyzing enough. You are using prepared queries that
have plans that get stale... you are not running autovac... You are
cursed (kidding)..
Joshua D. Drake
Thanks
Ralph
--
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.9/573 - Release Date:
5/12/2006 4:07 p.m.
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
