From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
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 09:13:51 +0800
Message-ID: <3FC2ACCF.2030303@familyhealth.com.au> (raw)
In-Reply-To: <2b1f01c3b2d6$c403ba70$0201a8c0@game>
References: <2b1f01c3b2d6$c403ba70$0201a8c0@game>
> 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. :]
Our busy website has a cronjob that runs VACUUM ANALYZE once an hour
(vacuumdb -a -q -z).
Have you tried going 'VACUUM FULL ANALYZE' (vacuumdb -a -q -z -f)
instead of a dump and reload?
Chris
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: chriskl@familyhealth.com.au, mk_spam@comcast.net
Subject: Re: Where to start for performance problem?
In-Reply-To: <3FC2ACCF.2030303@familyhealth.com.au>
* 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