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 BB1A0D1C96C for ; Tue, 25 Nov 2003 03:05:56 +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 16802-01 for ; Mon, 24 Nov 2003 23:05:29 -0400 (AST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by svr1.postgresql.org (Postfix) with ESMTP id B66F6D1C976 for ; Mon, 24 Nov 2003 23:05:24 -0400 (AST) Received: from game (12-250-179-10.client.attbi.com[12.250.179.10]) by comcast.net (sccrmhc12) with SMTP id <2003112503052801200l34a2e>; Tue, 25 Nov 2003 03:05:28 +0000 Message-ID: <2b8e01c3b301$0bc2f090$0201a8c0@game> Reply-To: "Nid" From: "Nid" To: "Christopher Kings-Lynne" Cc: References: <2b1f01c3b2d6$c403ba70$0201a8c0@game> <3FC2ACCF.2030303@familyhealth.com.au> Subject: Re: Where to start for performance problem? Date: Mon, 24 Nov 2003 21:05:56 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/235 X-Sequence-Number: 4795 I've been digging around in the code and found where we are executing the VACUUM command. VACUUM ANALYZE is executed every 15 minutes. We haven't tried VACUUM FULL ANALYZE. I think I read that using FULL is a good idea once a day or something. Just doing a VACUUM ANALYZE doesn't seem to be preventing our problem. Thank you for the responses. nid ----- Original Message ----- From: "Christopher Kings-Lynne" To: "MK Spam" Cc: Sent: Monday, November 24, 2003 7:13 PM Subject: Re: [PERFORM] Where to start for performance problem? > > 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 > > >