X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 2B6D49FB1C2 for ; Mon, 24 Jul 2006 04:54:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 90963-10 for ; Mon, 24 Jul 2006 04:54:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id 7C0919FB1B9 for ; Mon, 24 Jul 2006 04:54:12 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (p549D1A17.dip0.t-ipconnect.de [84.157.26.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 0268265874; Mon, 24 Jul 2006 09:55:57 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 043C718148BC2; Mon, 24 Jul 2006 09:54:30 +0200 (CEST) Message-ID: <44C47CB5.6080806@logix-tt.com> Date: Mon, 24 Jul 2006 09:54:29 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.2 (X11/20060516) MIME-Version: 1.0 To: pgsql-performance@postgresql.org, Alaa El Gohary , bruno@wolff.to Subject: Re: BUG #2543: Performance delay acrros the same day References: <200607210741.k6L7f2VL074357@wwwmaster.postgresql.org> <20060721183343.GA21995@wolff.to> In-Reply-To: <20060721183343.GA21995@wolff.to> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200607/233 X-Sequence-Number: 20093 Hi, Bruno, Bruno Wolff III wrote: > On Fri, Jul 21, 2006 at 07:41:02 +0000, > Alaa El Gohary wrote: >> The following bug has been logged online: > > The report below isn't a bug, its a performance question and should have > been sent to pgsql-performance@postgresql.org. I am redirecting replies there. > >> A query on the postgresql DB takes about 5 seconds and then it starts to >> take more time till it reaches about 60 seconds by the end of the same day. >> I tried vacuum but nothing changed the only thing that works is to dump the >> DB ,drop and create a new one with the dump taken. >> i need to know if there is any way to restore the performance back without >> the need for drop and create >> cause i can't do this accross the day > > You most likely aren't vacuuming often enough and/or don't have your FSM > setting high enough. Depending on the PostgreSQL version, it might also be that he suffers from index bloat. He might look into the manual pages about REINDEX for a description. HTH, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org