X-Original-To: pgsql-performance@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3B5ED474E44 for ; Fri, 7 Mar 2003 22:13:21 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h283DOub003241; Fri, 7 Mar 2003 22:13:25 -0500 (EST) To: Daniel Bruce Lynes Cc: PostgreSQL Performance Subject: Re: Stored Procedures and compiling In-reply-to: <200303071321.09981.dlynes@shaw.ca> References: <200303071321.09981.dlynes@shaw.ca> Comments: In-reply-to Daniel Bruce Lynes message dated "Fri, 07 Mar 2003 13:21:09 -0800" Date: Fri, 07 Mar 2003 22:13:24 -0500 Message-ID: <3240.1047093204@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/64 X-Sequence-Number: 1362 Daniel Bruce Lynes writes: > I am curious if there is any planned support for full stored procedure > compiling? I've seen that PostgreSQL does not compile the SQL code inside > plpgsql code. It is merely interpreted when the procedure gets called. This > is also documented in the main html documentation. > What I am wondering specifically is if stored procedure compiling will work > similar to Oracle's stored procedure compilation in the future? What exactly do you consider "compiling", and why do you think that whatever Oracle does (which you didn't bother to explain) is superior to what plpgsql does? regards, tom lane