X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 97ECED1B233 for ; Mon, 31 May 2004 08:01:32 -0300 (ADT) 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 51171-04 for ; Mon, 31 May 2004 08:01:32 -0300 (ADT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by svr1.postgresql.org (Postfix) with ESMTP id 3116ED1B3C6 for ; Mon, 31 May 2004 08:01:26 -0300 (ADT) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BUkXo-00035p-00 for ; Mon, 31 May 2004 13:01:28 +0200 Received: from srv.protecting.net ([212.126.218.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 31 May 2004 13:01:28 +0200 Received: from hf517 by srv.protecting.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 31 May 2004 13:01:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Harald Fuchs Subject: Re: Performance Problem Date: 31 May 2004 12:41:07 +0200 Organization: Linux Private Site Lines: 23 Message-ID: References: Reply-To: hf517@protecting.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: srv.protecting.net User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS X-Spam-Level: X-Archive-Number: 200405/337 X-Sequence-Number: 13653 In article , "Frank Smith" writes: > Hi > ID:77777 > I am running PostgreSQL 7.2.2 on Red Hat 9 and I am suffering a growing > performance problem. The problem shows through a slowing of queries and > an increase in the system CPU usage. Queries that took less than 6 > seconds clime to take more than 5 minutes and as the system is driven by > Apache through Perl scripts, the web server times out. Clearly I could > reset the Apache timers, however this would just hide the problem for a > little longer and of course once the problem starts to happen the system > tends to cascade because the users try again and the orphaned processes > continue to use processor time until they complete. > I use Cron to 'VACUUM ANALIZE' the system every night and this greatly > improved the performance but has not stopped the delay from growing. The > strange thing is that apart from the delay everything seems fine. If VACUUM does not stop the delay from growing, you might be suffering index bloat. Either REINDEX by crontab, or upgrade to 7.4, where VACUUM seems to take care of that.