Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 7C5B9B5DFBD for ; Wed, 8 Jun 2011 02:07:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 18623-05 for ; Wed, 8 Jun 2011 05:07:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from www.postnewspapers.com.au (www.postnewspapers.com.au [173.230.139.50]) by mail.postgresql.org (Postfix) with ESMTP id 3F281B5D800 for ; Wed, 8 Jun 2011 02:07:21 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by www.postnewspapers.com.au (Postfix) with ESMTP id BF95510D; Wed, 8 Jun 2011 01:07:20 -0400 (EDT) X-Virus-Scanned: amavisd-new at postnewspapers.com.au.com Received: from www.postnewspapers.com.au ([127.0.0.1]) by localhost (www.postnewspapers.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZoeY5XUTEsJf; Wed, 8 Jun 2011 01:07:20 -0400 (EDT) Received: from mail.postnewspapers.com.au (ppp171-128.static.internode.on.net [150.101.171.128]) by www.postnewspapers.com.au (Postfix) with ESMTP id DFC202D; Wed, 8 Jun 2011 01:07:19 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.postnewspapers.com.au (Postfix) with ESMTP id EA157AF10E; Wed, 8 Jun 2011 13:07:18 +0800 (WST) X-Virus-Scanned: Debian amavisd-new at postnewspapers.com.au Received: from mail.postnewspapers.com.au ([127.0.0.1]) by localhost (mail.postnewspapers.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Sm48mpC6D64J; Wed, 8 Jun 2011 13:07:13 +0800 (WST) Received: from [10.1.1.3] (58-7-128-152.dyn.iinet.net.au [58.7.128.152]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Craig Ringer", Issuer "POST Certificate Authority" (verified OK)) by mail.postnewspapers.com.au (Postfix) with ESMTPSA id BAAF4AEAA5; Wed, 8 Jun 2011 13:07:13 +0800 (WST) Message-ID: <4DEF037E.9020105@postnewspapers.com.au> Date: Wed, 08 Jun 2011 13:07:10 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: bakkiya CC: pgsql-performance@postgresql.org Subject: Re: 100% CPU Utilization when we run queries. References: <1307506768241-4465765.post@n5.nabble.com> In-Reply-To: <1307506768241-4465765.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.788 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, URI_HEX=1.122 X-Spam-Level: X-Archive-Number: 201106/52 X-Sequence-Number: 43985 On 8/06/2011 12:19 PM, bakkiya wrote: > We have a postgresql 8.3.8 DB which consumes 100% of the CPU whenever we run > any query. Yep, that's what it's supposed to do if it's not I/O limited. What's the problem? Is the query taking longer than you think it should to execute? Do you expect it to be waiting for disk rather than CPU? Please show your problem query/queries, and EXPLAIN ANALYZE output. See: http://wiki.postgresql.org/wiki/Guide_to_reporting_problems > http://postgresql.1045698.n5.nabble.com/file/n4465765/untitled.bmp Heh. That's been resized to a 250x250 bitmap, which isn't exactly useful or readable. Why not paste the text rather than a screenshot? -- Craig Ringer Tech-related writing at http://soapyfrogs.blogspot.com/