From: Josh Berkus <josh@agliodbs.com>
To: Rodrigo Sakai <rodrigo@2bfree.com.br>
To: pgsql-sql@postgresql.org
Subject: Re: Compiling pl/pgsql functions
Date: Thu, 19 Feb 2004 11:26:26 -0800
Message-ID: <200402191126.26465.josh@agliodbs.com> (raw)
In-Reply-To: <20040219180521.31448.qmail@hm10.locaweb.com.br>
References: <20040219180521.31448.qmail@hm10.locaweb.com.br>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, rodrigo@2bfree.com.br
Subject: Re: Compiling pl/pgsql functions
In-Reply-To: <200402191126.26465.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox