From: Aaron Bono <postgresql@aranya.com>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: carlosreimer@terra.com.br
Cc: rodrigo.sakai@zanthus.com.br
Cc: pgsql-admin@postgresql.org
Subject: Re: Hiding table structure information
Date: Mon, 26 Jun 2006 19:48:32 -0500
Message-ID: <bf05e51c0606261748v6188d251qb515466b71e17d48@mail.gmail.com> (raw)
In-Reply-To: <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com>
References: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS>
<PEEPKDFEHHEMKBBFPOOKMENNDBAA.carlosreimer@terra.com.br>
<36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com>
Would there be a way to set up the 2 databases - one with the tables and
data and the other that connects to the first with views into the second
database?
Actually I am interested because I will soon need to set up a way to feed
data to multiple databases and would love to have a stored procedure or
trigger that, when the data is updated in one database, the changes are
propagated to all the other databases.
Thanks,
Aaron
On 6/26/06, Jonah H. Harris <jonah.harris@gmail.com> wrote:
>
> On 6/26/06, Carlos H. Reimer <carlosreimer@terra.com.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@enterprisedb.com
> Iselin, New Jersey 08830 | http://www.enterprisedb.com/
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: postgresql@aranya.com, jonah.harris@gmail.com, carlosreimer@terra.com.br, rodrigo.sakai@zanthus.com.br
Subject: Re: Hiding table structure information
In-Reply-To: <bf05e51c0606261748v6188d251qb515466b71e17d48@mail.gmail.com>
References: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS> <PEEPKDFEHHEMKBBFPOOKMENNDBAA.carlosreimer@terra.com.br> <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com> <bf05e51c0606261748v6188d251qb515466b71e17d48@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox