X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C70063A4498 for ; Wed, 17 Nov 2004 23:38:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 62473-03 for ; Wed, 17 Nov 2004 23:38:45 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 585BE3A4492 for ; Wed, 17 Nov 2004 23:38:47 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iAHNceHa005434; Wed, 17 Nov 2004 18:38:41 -0500 (EST) To: "silviapg@tiscali.it" Cc: pgsql-performance@postgresql.org, josh@agliodbs.com Subject: Re: postgres eating CPU In-reply-to: <419BD5DF.5090902@tiscali.it> References: <419BCD20.4010906@tiscali.it> <200411171427.13134.josh@agliodbs.com> <419BD5DF.5090902@tiscali.it> Comments: In-reply-to "silviapg@tiscali.it" message dated "Wed, 17 Nov 2004 23:51:11 +0100" Date: Wed, 17 Nov 2004 18:38:40 -0500 Message-ID: <5433.1100734720@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=TO_ADDRESS_EQ_REAL X-Spam-Level: X-Archive-Number: 200411/271 X-Sequence-Number: 9225 "silviapg@tiscali.it" writes: > in March there was an interesting discussion on the list with the > subject "postgres eating CPU on HP9000". > http://archives.postgresql.org/pgsql-performance/2004-03/msg00380.php Reviewing that, the problem is most likely that (a) they didn't have max_fsm_pages set high enough to cover the database, and (b) they were running 7.3.* which is prone to index bloat. regards, tom lane