| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Trevor Talbot <quension(at)gmail(dot)com>, "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: viewing source code |
| Date: | 2007-12-20 20:07:39 |
| Message-ID: | 20071220200739.GC11586@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Joshua D. Drake escribió:
> I don't know that it needs to be that extensive. I noted elsewhere in
> the thread the idea of a plpgsql_s. I think that is an interesting
> idea. I just don't think it needs to be incorporated into
> postgresql-core.
I don't think that makes any kind of sense. Hiding prosrc should happen
on a entirely different level from the language on which the function is
written. It's a completely orthogonal decision. Besides, you probably
don't want prosrc to be encrypted -- just not accesible to everyone, and
it doesn't make sense to have a different _language_ to do that.
Also, having an encrypted source code means there must be a decryption
key somewhere, which is a pain on itself. And if you expose the crypted
prosrc, you are exposing to brute force attacks (to which you are not if
prosrc is hidden).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-12-20 20:17:34 | Re: viewing source code |
| Previous Message | Roberts, Jon | 2007-12-20 20:02:57 | Re: viewing source code |