Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 94BD6632871
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  6 Jul 2010 11:33:18 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 81224-09 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  6 Jul 2010 14:33:02 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.187])
	by mail.postgresql.org (Postfix) with ESMTP id 526C163237A
	for <pgsql-admin@postgresql.org>; Tue,  6 Jul 2010 11:33:01 -0300 (ADT)
Received: from [192.168.0.242] (87-224-90-195.spitfireuk.net [87.224.90.195])
	by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis)
	id 0Lmwns-1P4LtH1zFE-00hLBq; Tue, 06 Jul 2010 16:32:59 +0200
Message-ID: <4C333E9A.5060600@2ndquadrant.com>
Date: Tue, 06 Jul 2010 15:32:58 +0100
From: Greg Smith <greg@2ndquadrant.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: higeon <higeon@gmail.com>
CC: pgsql-admin@postgresql.org
Subject: Re: Postmaster taking up 100% of CPU
References: <AANLkTilaoyL2RcTu4he-iDU9MKSYATU7qQEWfxopF4l7@mail.gmail.com>
In-Reply-To: <AANLkTilaoyL2RcTu4he-iDU9MKSYATU7qQEWfxopF4l7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:kQZolXkNidAyz4AgfMUmSeU2e+pS8NGX2Jt28tXpIpa
	AMWPjU2M7O5b+wv+bhvpyU7xJf3OXMHo3AFue8AOpFC1ZEZUft
	vwGNpXTVgqfjnAWA9rlVeqE2e8c2Cv+e5x7KWxve/PM/Sr7SkA
	2ZnsFQmMYn8oORvVCr7ip2wb/JglpuPj056W92bSD8d7IePrwF
	aTqBe93IquBWphsF6JHDKK5D6WiAoKwWe7qgfJtLUs=
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	RCVD_IN_DNSWL_NONE=-0.0001
X-Spam-Level: 
X-Archive-Number: 201007/13
X-Sequence-Number: 35032

higeon wrote:
> The following is my top log and ps log:

Try using "top -c" on Linux instead.  Then you'll be able to see what 
all the processes are doing.  Any heavy query will cause a CPU to 
consume 100% of its time when running, so there may be nothing wrong 
other than you have queries to optimize better.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us