> One big reason why nothing hasn't been done is that
> there is a decent
> 'low tech' obfuscation tactic already: remove
> select access from
> pg_proc to the user accounts in question and
> 'public'.  This will
> essentially disable casual browsing of procedure code from
> user
> accounts.

Neat :-)




-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to