Message-ID: <464CDF0A.5050309@commandprompt.com>
Date: Thu, 17 May 2007 16:02:34 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: Ralph Mason <ralph.mason@telogis.com>
CC: pgsql-performance@postgresql.org
Subject: Re: Ever Increasing IOWAIT
References: <011b01c798d5$141365a0$3c3a30e0$@mason@telogis.com>
In-Reply-To: <011b01c798d5$141365a0$3c3a30e0$@mason@telogis.com>
Content-Type: text/plain; charset=windows-1250; format=flowed
Content-Transfer-Encoding: quoted-printable

Ralph Mason wrote:
> We have a database running on a 4 processor machine.  As time goes by=20
> the IO gets worse and worse peeking at about 200% as the machine loads =
up.
>=20
> =20
>=20
> The weird thing is that if we restart postgres it=92s fine for hours bu=
t=20
> over time it goes bad again.
>=20
> =20
>=20
> (CPU usage graph here=20
> http://www.flickr.com/photos/8347741@N02/502596262/ )  You can clearly =

> see where the restart happens in the IO area
>=20
> =20
>=20
> This is Postgres  8.1.4 64bit.

1. Upgrade to 8.1.9. There is a bug with autovac that is fixed that is=20
pretty important.

>=20
> =20
>=20
> Anyone have any ideas?
>=20

Sure... you aren't analyzing enough. You are using prepared queries that =

have plans that get stale... you are not running autovac... You are=20
cursed (kidding)..

Joshua D. Drake

> =20
>=20
> Thanks
>=20
> Ralph
>=20
> =20
>=20
>=20
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.15.9/573 - Release Date:=20
> 5/12/2006 4:07 p.m.
>=20


--=20

       =3D=3D=3D The PostgreSQL Company: Command Prompt, Inc. =3D=3D=3D
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/