X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E8AB4D1DF05 for ; Thu, 19 Feb 2004 20:49:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 21910-02 for ; Thu, 19 Feb 2004 16:49:16 -0400 (AST) Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by svr1.postgresql.org (Postfix) with ESMTP id 009E1D1D1A4 for ; Thu, 19 Feb 2004 16:49:15 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 1Atv6g-000M92-0U; Thu, 19 Feb 2004 20:49:14 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id CE4EE1597E; Thu, 19 Feb 2004 20:49:12 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 8EF9815945; Thu, 19 Feb 2004 20:49:10 +0000 (GMT) From: Richard Huxton To: josh@agliodbs.com, "Rodrigo Sakai" , pgsql-sql@postgresql.org Subject: Re: Compiling pl/pgsql functions Date: Thu, 19 Feb 2004 20:49:09 +0000 User-Agent: KMail/1.5 References: <20040219180521.31448.qmail@hm10.locaweb.com.br> <200402191126.26465.josh@agliodbs.com> In-Reply-To: <200402191126.26465.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402192049.09624.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/288 X-Sequence-Number: 16978 On Thursday 19 February 2004 19:26, Josh Berkus wrote: > Rodrigo, > > > I insist in my question, is there a way to compile the plpgsql codes or > > something like that, or its better to think about writting this postgres > functions in C?????? > > No, there is not. Nor is there likely to be for any PL, as it would add > significant overhead for no real gain. It's worse than that - if you really denied access to them, you wouldn't be able to dump/restore the database - absolute nightmare. > Personally, I find it > hard to believe that any of my PL/SQL functions (or yours) are so brilliant > that they need trade secret protection. Some of mine are so ugly, I wish they were hidden away mind you ;-) -- Richard Huxton Archonet Ltd