Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 1F6BE9FA1D6 for ; Tue, 24 Apr 2007 03:33:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 76537-04 for ; Tue, 24 Apr 2007 03:33:16 -0300 (ADT) 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 933C59FA2A6 for ; Tue, 24 Apr 2007 03:33:17 -0300 (ADT) 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 l3O6XD2e024507; Tue, 24 Apr 2007 02:33:13 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org Subject: Re: pl/pgsql function spikes CPU 100% In-reply-to: References: <6522.1174056565@sss.pgh.pa.us> Comments: In-reply-to Jeff Frost message dated "Mon, 23 Apr 2007 23:18:20 -0700" Date: Tue, 24 Apr 2007 02:33:13 -0400 Message-ID: <24506.1177396393@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/213 X-Sequence-Number: 25277 Jeff Frost writes: > Well, finally got this system upgraded to 8.1.8, but unfortunately, that did > not resolve this. Is there any reasonable way to see where this function is > spending it's time? I've grown enamored of oprofile lately --- if you're on a recent Linux system, try that. Solaris' DTrace is said to have equivalent capability. On other systems you could consider plain 'ol gprof. Any of these will require a certain amount of man-page-reading :-( regards, tom lane