| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: viewing source code |
| Date: | 2007-12-18 04:51:13 |
| Message-ID: | Pine.BSO.4.64.0712172348130.8691@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 17 Dec 2007, Merlin Moncure wrote:
> the table is pg_proc. you have to revoke select rights from public
> and the user of interest. be aware this will make it very difficult
> for that user to do certain things in psql and (especially) pgadmin.
> it works.
>
> a better solution to this problem is to make a language wrapper for
> pl/pgsql that encrypts the source on disk. afaik, no one is working on
> th is. it would secure the code from remote users but not necessarily
> from people logged in to the server. the pg_proc hack works ok
> though.
>
Another enhancement that would improve this situation would be to
implement per column permissions as the sql spec has, so that you could
revoke select on just the prosrc column and allow clients to retrieve the
metadata they need.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-12-18 09:05:26 | Re: Evaluation of PG performance vs MSDE/MSSQL 2000 (not 2005) |
| Previous Message | Robert Bernabe | 2007-12-18 04:31:44 | Re: Evaluation of PG performance vs MSDE/MSSQL 2000 (not 2005) |