X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 93609D1EA82 for ; Mon, 29 Mar 2004 20:24:01 +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 63889-10 for ; Mon, 29 Mar 2004 16:24:00 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 3CA46D1EA4B for ; Mon, 29 Mar 2004 16:23:58 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4727200; Mon, 29 Mar 2004 12:25:19 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Fabio Esposito Subject: Re: postgres eating CPU on HP9000 Date: Mon, 29 Mar 2004 12:23:27 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403291223.27213.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/416 X-Sequence-Number: 6272 Fabio, > The Vacuum's don't take too long, 10 minutes at most. I can tell from ps > -ef | grep and top that its the selects/inserts/updates from the postgres > related to our app that take all that time up. If we rerun initdb and > reload the data, it works great for about two days, then goes bad again. > > We are in the process of trying out 7.4.2 right now, just waiting on the > reload of pg_dump. Well, test running VACUUM ANALYZE as the "postgres" superuser and see if that fixes the issue. -- -Josh Berkus Aglio Database Solutions San Francisco