From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: "Rodrigo Sakai" <rodrigo@2bfree.com.br>, pgsql-sql@postgresql.org
Subject: Re: Compiling pl/pgsql functions
Date: Thu, 19 Feb 2004 11:26:26 -0800
User-Agent: KMail/1.5.4
References: <20040219180521.31448.qmail@hm10.locaweb.com.br>
In-Reply-To: <20040219180521.31448.qmail@hm10.locaweb.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402191126.26465.josh@agliodbs.com>

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.

You have, as I see it, 3 choices:

1) You can give up on code obfuscation and simply provide the functions 
normally, and rely on your contracts and copyright law to protect your code.  
This is what I do, and I feel pretty strongly that code obfuscation is a dumb 
and ineffective way to protect copyright.   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.

2) You can write your functions in C and compile them.

3) You can carefully engineer your database permissions so that the user can 
have almost full DBA powers without being the superuser, and deny them direct 
access to the pg_proc table.   This would be a real PITA, though.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco