From: Harald Fuchs <hf517@protecting.net>
To: pgsql-admin@postgresql.org
Subject: Re: Performance Problem
Date: 31 May 2004 12:41:07 +0200
Message-ID: <pufz9gg9q4.fsf@srv.protecting.net> (raw)
References: <s0b610a3.089@uk.aeat.com>
In article <s0b610a3.089@uk.aeat.com>,
"Frank Smith" <frank.smith@aeat.co.uk> writes:
> Hi
> ID:77777
> I am running PostgreSQL 7.2.2 on Red Hat 9 and I am suffering a growing
> performance problem. The problem shows through a slowing of queries and
> an increase in the system CPU usage. Queries that took less than 6
> seconds clime to take more than 5 minutes and as the system is driven by
> Apache through Perl scripts, the web server times out. Clearly I could
> reset the Apache timers, however this would just hide the problem for a
> little longer and of course once the problem starts to happen the system
> tends to cascade because the users try again and the orphaned processes
> continue to use processor time until they complete.
> I use Cron to 'VACUUM ANALIZE' the system every night and this greatly
> improved the performance but has not stopped the delay from growing. The
> strange thing is that apart from the delay everything seems fine.
If VACUUM does not stop the delay from growing, you might be suffering
index bloat. Either REINDEX by crontab, or upgrade to 7.4, where
VACUUM seems to take care of that.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: hf517@protecting.net
Subject: Re: Performance Problem
In-Reply-To: <pufz9gg9q4.fsf@srv.protecting.net>
References: <s0b610a3.089@uk.aeat.com> <pufz9gg9q4.fsf@srv.protecting.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox