X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CF896528C1 for ; Mon, 27 Jun 2005 23:49:27 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 82717-02 for ; Tue, 28 Jun 2005 02:49:21 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 2E018528A9 for ; Mon, 27 Jun 2005 23:49:20 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j5S2nJHA084521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Jun 2005 20:49:22 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j5S2nJto017780; Mon, 27 Jun 2005 20:49:19 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j5S2nJ02017779; Mon, 27 Jun 2005 20:49:19 -0600 (MDT) (envelope-from mfuhr) Date: Mon, 27 Jun 2005 20:49:18 -0600 From: Michael Fuhr To: "Karl O. Pinc" Cc: pgsql-performance@postgresql.org Subject: Re: Performance analysis of plpgsql code Message-ID: <20050628024918.GA17735@winnie.fuhr.org> References: <1119915045l.4428l.5l@mofo> <20050627233303.GA17069@winnie.fuhr.org> <1119923648l.11411l.0l@mofo> <20050628013419.GA17407@winnie.fuhr.org> <1119927786l.11411l.3l@mofo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1119927786l.11411l.3l@mofo> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/518 X-Sequence-Number: 13155 On Tue, Jun 28, 2005 at 03:03:06AM +0000, Karl O. Pinc wrote: > > For all your work a documentation patch is appended that > I think is easier to read and might avoid this problem > in the future. Patches should go to the pgsql-patches list -- the people who review and apply patches might not be following this thread. -- Michael Fuhr http://www.fuhr.org/~mfuhr/