| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Juan Cuervo (Quality Telecom)" <juanrcuervo(at)quality-telecom(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: revoked permissions on table still allows users to see table's structure |
| Date: | 2011-07-22 01:48:44 |
| Message-ID: | CAOR=d=1Zoo6K55wfkBpb_rx2Jb2ox_Lp5WBN1dGmYMLD3x=ADg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Jul 21, 2011 at 6:08 PM, Juan Cuervo (Quality Telecom)
<juanrcuervo(at)quality-telecom(dot)net> wrote:
> Hi All
>
> I'm new to the list, but have a few years as postgres user. I want to share
> what I consider a rare behavior of postgresql regarding database object's
> premissions:
>
> I have noticed that there is no way (at least no one I know) to prevent a
> user from seeing the table's structures in a database.
>
> Is this a normal behavior of the product ?
Yep. Completely normal.
> Is there a way to prevent a user from seeing my table's, procedure's and
> function's code ?
Don't let them connect to the db? That's all I can think of.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johann Spies | 2011-07-22 08:55:51 | Re: Out of memory |
| Previous Message | Juan Cuervo (Quality Telecom) | 2011-07-22 00:08:14 | revoked permissions on table still allows users to see table's structure |