From: Bruno Wolff III <bruno@wolff.to>
To: MK Spam <mk_spam@comcast.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Where to start for performance problem?
Date: Tue, 25 Nov 2003 10:52:32 -0600
Message-ID: <20031125165232.GA25043@wolff.to> (raw)
In-Reply-To: <2b1f01c3b2d6$c403ba70$0201a8c0@game>
References: <2b1f01c3b2d6$c403ba70$0201a8c0@game>
On Mon, Nov 24, 2003 at 16:03:17 -0600,
MK Spam <mk_spam@comcast.net> wrote:
>
> The archives of this list provides many ideas for improving performance, but the problem we are having is gradually degrading performance ending in postgres shutting down. So it's not a matter of optimizing a complex query to take 5 seconds instead of 60 seconds. From what I can tell we are using the VACUUM command on a schedule but it doesn't seem to prevent the database from becoming "congested" as we refer to it. :] Anyway, the only way I know to "fix" the problem is to export (pg_dump) the db, drop the database, recreate the database and import the dump. This seems to return performance back to normal but obviously isn't a very good "solution". The slowdown and subsequent crash can take as little as 1 week for databases with a lot of data or go as long as a few weeks to a month for smaller data sets.
A couple of things you might look for are index bloat and having FSM set too
small for your plain vacuums. Upgrading to 7.4 may help with index bloat
if that is your problem.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, mk_spam@comcast.net
Subject: Re: Where to start for performance problem?
In-Reply-To: <20031125165232.GA25043@wolff.to>
* 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