Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 6A98A475D18 for ; Fri, 12 Apr 2002 14:58:54 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3CIwBF29465; Fri, 12 Apr 2002 14:58:11 -0400 (EDT) To: Jan Wieck Cc: Peter Eisentraut , Gordon Clarke , pgsql-sql@postgresql.org Subject: Re: Functions in Postgres In-reply-to: <200204121846.g3CIk2U07447@saturn.janwieck.net> References: <200204121846.g3CIk2U07447@saturn.janwieck.net> Comments: In-reply-to Jan Wieck message dated "Fri, 12 Apr 2002 14:46:02 -0400" Date: Fri, 12 Apr 2002 14:58:11 -0400 Message-ID: <29462.1018637891@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/163 X-Sequence-Number: 7427 Jan Wieck writes: > Tom Lane wrote: >> Not since about Tcl 8.0. > You're right, not Tcl's fault. Noone changed PL/Tcl to use it > though. It still does Tcl_CreateCommand(), which is the > backward compatibility pure string interface wrapping > technology. :-) I could be mistaken, but I thought Tcl would still reduce the function text to bytecode behind-the-scenes. We are losing with unnecessary text conversions in a number of places in pltcl, but I think it's just in parameter passing at pltcl function entry/exit and calls to the special Tcl commands provided by pltcl. If you're executing regular Tcl commands inside a pltcl function, I think you still will get benefit from Tcl 8's speedups. regards, tom lane