Tom Lane wrote:
> For example, something I've heard repeatedly is that people would like to
> hide the source code of their SQL or PLxxx functions from users who are
> nonetheless allowed to call those functions. A row-wise selective view of
> pg_proc can't fix that. In many cases it's less than clear which rows of
> which catalogs to hide anyway.
It wouldn't be terribly difficult to encrypt prosrc with 3des (or maybe aes)
using the owner's passwd from pg_shadow. We would need a new bool column in
pg_proc (proisencrypted?) and some logic in fmgr.c.
Is there sufficient interest to justify the effort?
Joe
