Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 247214762E7 for ; Fri, 3 Jan 2003 12:19:28 -0500 (EST) Received: from www.e-servicesystem.com (s64-180-126-48.bc.hsia.telus.net [64.180.126.48]) by postgresql.org (Postfix) with ESMTP id 2283C4760E4 for ; Fri, 3 Jan 2003 12:19:27 -0500 (EST) Received: from power (dmz_gw.e-servicesystem.com [192.168.147.3]) by www.e-servicesystem.com (8.11.2/8.11.2) with ESMTP id h03HQMY16049 for ; Fri, 3 Jan 2003 09:26:22 -0800 Content-Type: text/plain; charset="gb2312" From: Daniel Bruce Lynes To: pgsql-sql@postgresql.org Subject: Compiling pl/pgsql functions? Date: Fri, 3 Jan 2003 09:27:28 -0800 X-Mailer: KMail [version 1.4] MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301030927.28989.dlynes@shaw.ca> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/25 X-Sequence-Number: 10890 Through preliminary examination, it appears stored procedures using pl/pgsq= l=20 in PostgreSQL 7.3 are interpreted, rather than compiled? When we insert a stored function into PostgreSQL, the syntax check is not d= one=20 until execution, and only on the branch/path of execution, not on the entir= e=20 function. Is there any way to precompile the pl/pgsql functions so that we know if=20 there's a missing object dependency upon function creation, rather than at= =20 runtime? Thanks in advance.