X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (unknown [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C8CB79FB31D for ; Wed, 30 Aug 2006 11:03:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 31449-04-3 for ; Wed, 30 Aug 2006 11:03:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from globalrelay.com (mail1.globalrelay.com [216.18.71.77]) by postgresql.org (Postfix) with ESMTP id A4C499FB309 for ; Wed, 30 Aug 2006 11:03:05 -0300 (ADT) X-Virus-Scanned: Scanned by GRC-AntiVirus Gateway X-GR-Acctd: YES Received: from [67.90.96.2] (HELO DaveEMachine) by globalrelay.com (CommuniGate Pro SMTP 4.2.3) with ESMTP id 102326943; Wed, 30 Aug 2006 07:03:01 -0700 From: "Dave Dutcher" To: "'Willo van der Merwe'" Cc: Subject: Re: PostgreSQL performance issues Date: Wed, 30 Aug 2006 09:03:01 -0500 Message-ID: <007501c6cc3d$01e1e290$8300a8c0@tridecap.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0076_01C6CC13.190BDA90" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: <44F58EC9.9090703@studentvillage.co.za> Importance: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.202 tagged_above=0 required=5 tests=AWL, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200608/476 X-Sequence-Number: 20661 This is a multi-part message in MIME format. ------=_NextPart_000_0076_01C6CC13.190BDA90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable That's an interesting situation. Your CPU's are pegged, and you're = hardly doing any IO. I wonder if there is some ineficient query, or if its = just very high query volume. Maybe you could try setting log_min_duration_statement to try to track down the slowest of the = queries. Then post the slow queries with an explain analyze to the list. =20 Here is some info on setting up logging: http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.htm= l =20 Are your queries standard SQL or do you call functions you wrote in = PL/pgSQl or PL/Python or anything? =20 =20 ------=_NextPart_000_0076_01C6CC13.190BDA90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
That's an=20 interesting situation.  Your CPU's are pegged, and you're hardly = doing any=20 IO.  I wonder if there is some ineficient query, or if its just = very high=20 query volume.  Maybe you could try setting = log_min_duration_statement to=20 try to track down the slowest of the queries.  Then post the slow = queries=20 with an explain analyze to the list.
 
Here = is some info=20 on setting up logging:
http://www.postgresql.org/docs/8.1/interactive/runtime-config-= logging.html
 
Are = your queries=20 standard SQL or do you call functions you wrote in PL/pgSQl or PL/Python = or=20 anything?
 
 
------=_NextPart_000_0076_01C6CC13.190BDA90--