| From: | Christophe <xof(at)thebuild(dot)com> |
|---|---|
| To: | Postgres General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Oracle and Postgresql |
| Date: | 2008-09-15 21:29:37 |
| Message-ID: | 72BF0055-2123-4D9B-B407-9C60C98DC5B0@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-www |
On Sep 15, 2008, at 1:15 PM, Scott Marlowe wrote:
> I wasn't kidding up there. Setting view permissions on plpgsql (or
> any pl code really) would be understandable. If you're not a super
> user or the owner, you need permission to see it.
Ah, sorry, I parsed that as needing permission to see the code of the
Pl/pgSQL interpreter.
> But whether it's oracle or postgresql, this is just security through
> obscurity. If you have root access on the server either method would
> be trivial to hack.
Oh, sure. (Same is true of Oracle, of course.) I wouldn't use it
myself, but if this is a feature-checkbox item, that's how you'd need
to go about doing it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Magoffin | 2008-09-15 21:32:41 | Re: Out of memory on SELECT (from sort?) in 8.3 |
| Previous Message | Matt Magoffin | 2008-09-15 21:28:09 | Re: Out of memory on SELECT (from sort?) in 8.3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-09-15 21:40:01 | Re: Oracle and Postgresql |
| Previous Message | Merlin Moncure | 2008-09-15 21:24:40 | Re: Oracle and Postgresql |