Received: from sss2.sss.pgh.pa.us (root@sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e77FqWG36992 for ; Mon, 7 Aug 2000 11:52:32 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id LAA06294; Mon, 7 Aug 2000 11:52:18 -0400 (EDT) To: Philip Warner cc: Ang Chin Han , pgsql-sql@postgresql.org Subject: Re: Functions too slow, even with iscachable? In-reply-to: <3.0.5.32.20000808010738.0281eca0@mail.rhyme.com.au> References: <20000807171110.A31838@pintoo.com> <20000807171110.A31838@pintoo.com> <3.0.5.32.20000808010738.0281eca0@mail.rhyme.com.au> Comments: In-reply-to Philip Warner message dated "Tue, 08 Aug 2000 01:07:38 +1000" Date: Mon, 07 Aug 2000 11:52:18 -0400 Message-ID: <6291.965663538@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/56 Philip Warner writes: > At 10:58 7/08/00 -0400, Tom Lane wrote: >> Looks like we need to teach the optimizer that expressions involving >> params can be treated like simple params for the purposes of >> optimization. > So long as the function is cacheable... Yes, of course --- but the same problem currently arises for cases like "var = param + 1" ... regards, tom lane