From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | carlosreimer(at)terra(dot)com(dot)br |
Cc: | rodrigo(dot)sakai(at)zanthus(dot)com(dot)br, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Hiding table structure information |
Date: | 2006-06-26 21:07:06 |
Message-ID: | 36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 6/26/06, Carlos H. Reimer <carlosreimer(at)terra(dot)com(dot)br> wrote:
> Maybe the question should be reformulted to: is there a way to hide
> pg_catalog schema? I think it can?t not be done because all metadata are
> there, but maybe somebody can see a solution.
You could use a set returning function and a view to hide the original
table's details. As for hiding pg_catalog... I believe you could
create a rule on it.
Never tried to hide something this extensively... and don't really
understand a practical reason for doing so. Remember, security
through obscurity is flawed from the get go.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Diego Gaviola | 2006-06-26 22:46:29 | unsubscribe |
Previous Message | Tom Lane | 2006-06-26 21:06:49 | Re: RES: Hiding table structure information |