Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 9285C2E0057 for ; Wed, 16 Apr 2008 12:10:16 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 38621-04-2 for ; Wed, 16 Apr 2008 12:10:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id B31572E0069 for ; Wed, 16 Apr 2008 12:10:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m3GF9lZY008329; Wed, 16 Apr 2008 11:09:47 -0400 (EDT) To: "Gavin M. Roy" cc: pgsql-performance@postgresql.org Subject: Re: SQL Function Slowness, 8.3.0 In-reply-to: References: Comments: In-reply-to "Gavin M. Roy" message dated "Wed, 16 Apr 2008 11:06:35 -0400" Date: Wed, 16 Apr 2008 11:09:47 -0400 Message-ID: <8328.1208358587@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/201 X-Sequence-Number: 29694 "Gavin M. Roy" writes: > In 8.3.0, I'm seeing some oddities with SQL functions which I thought were > immune to the planner data restrictions of plpgsql functions and the sort. Without a specific example this discussion is pretty content-free, but in general SQL functions face the same hazards of bad parameterized plans as plpgsql functions do. regards, tom lane