X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D16CBD1C914 for ; Tue, 25 Nov 2003 01:12:09 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 88612-04 for ; Mon, 24 Nov 2003 21:11:41 -0400 (AST) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id A0F7DD1C951 for ; Mon, 24 Nov 2003 21:11:36 -0400 (AST) Received: from familyhealth.com.au (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (8.12.9p1/8.12.9) with ESMTP id hAP1BGoD032541; Tue, 25 Nov 2003 09:11:18 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <3FC2ACCF.2030303@familyhealth.com.au> Date: Tue, 25 Nov 2003 09:13:51 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MK Spam Cc: pgsql-performance@postgresql.org Subject: Re: Where to start for performance problem? References: <2b1f01c3b2d6$c403ba70$0201a8c0@game> In-Reply-To: <2b1f01c3b2d6$c403ba70$0201a8c0@game> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/231 X-Sequence-Number: 4791 > 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