Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1915C9FA4B6 for ; Thu, 8 Feb 2007 14:46:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 75653-05 for ; Thu, 8 Feb 2007 14:46:32 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3B7869FB2B2 for ; Thu, 8 Feb 2007 14:46:33 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l18IkVlS007995; Thu, 8 Feb 2007 13:46:31 -0500 (EST) To: Benjamin Minshall cc: pgsql-performance@postgresql.org Subject: Re: stats collector process high CPU utilization In-reply-to: <45CB5D06.7090004@intellicon.biz> References: <45CB5441.1040707@intellicon.biz> <21013.1170955076@sss.pgh.pa.us> <45CB5D06.7090004@intellicon.biz> Comments: In-reply-to Benjamin Minshall message dated "Thu, 08 Feb 2007 12:25:26 -0500" Date: Thu, 08 Feb 2007 13:46:31 -0500 Message-ID: <7994.1170960391@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/90 X-Sequence-Number: 23144 Benjamin Minshall writes: > Tom Lane wrote: >> Benjamin Minshall writes: >>> Since upgrading to 8.2.3 yesterday, the stats collector process has had >>> very high CPU utilization; it is consuming roughly 80-90% of one CPU. >>> The server seems a lot more sluggish than it was before. Is this normal >>> operation for 8.2 or something I should look into correcting? >> What version did you update from, and what platform is this? > I upgraded from 8.1.5. The system is a dual Xeon 2.4Ghz, 4Gb RAM > running linux kernel 2.6 series. OK, I was trying to correlate it with post-8.2.0 patches but evidently that's the wrong tree to bark up. No, this isn't an expected behavior. Is there anything unusual about your database (huge numbers of tables, or some such)? Can you gather some info about what it's doing? strace'ing the stats collector might prove interesting, also if you have built it with --enable-debug then oprofile results would be helpful. regards, tom lane