pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedHiding table structure information
6+ messages / 5 participants
[nested] [flat]
* Hiding table structure information
@ 2006-06-26 17:39 Carlos H. Reimer <carlosreimer@terra.com.br>
0 siblings, 0 replies; 6+ messages in thread
From: Carlos H. Reimer @ 2006-06-26 17:39 UTC (permalink / raw)
To: pgsql-admin
Hello,
Is there a way to hide the table definition structure from an user, even if
the user has privileges to select data from that table?
Reimer
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hiding table structure information
@ 2006-06-26 21:07 Jonah H. Harris <jonah.harris@gmail.com>
2006-06-27 00:48 ` Re: Hiding table structure information Aaron Bono <postgresql@aranya.com>
0 siblings, 1 reply; 6+ messages in thread
From: Jonah H. Harris @ 2006-06-26 21:07 UTC (permalink / raw)
To: carlosreimer@terra.com.br; +Cc: rodrigo.sakai@zanthus.com.br; pgsql-admin
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/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hiding table structure information
2006-06-26 21:07 Re: Hiding table structure information Jonah H. Harris <jonah.harris@gmail.com>
@ 2006-06-27 00:48 ` Aaron Bono <postgresql@aranya.com>
2006-06-27 16:01 ` Re: Hiding table structure information Bruno Wolff III <bruno@wolff.to>
2006-06-28 00:31 ` Re: Hiding table structure information Jim Nasby <jnasby@pervasive.com>
0 siblings, 2 replies; 6+ messages in thread
From: Aaron Bono @ 2006-06-27 00:48 UTC (permalink / raw)
To: Jonah H. Harris <jonah.harris@gmail.com>; +Cc: carlosreimer@terra.com.br; rodrigo.sakai@zanthus.com.br; pgsql-admin
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/
>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hiding table structure information
2006-06-26 21:07 Re: Hiding table structure information Jonah H. Harris <jonah.harris@gmail.com>
2006-06-27 00:48 ` Re: Hiding table structure information Aaron Bono <postgresql@aranya.com>
@ 2006-06-27 16:01 ` Bruno Wolff III <bruno@wolff.to>
2006-06-27 18:18 ` Re: Hiding table structure information Aaron Bono <postgresql@aranya.com>
1 sibling, 1 reply; 6+ messages in thread
From: Bruno Wolff III @ 2006-06-27 16:01 UTC (permalink / raw)
To: Aaron Bono <postgresql@aranya.com>; +Cc: Jonah H. Harris <jonah.harris@gmail.com>; carlosreimer@terra.com.br; rodrigo.sakai@zanthus.com.br; pgsql-admin
On Mon, Jun 26, 2006 at 19:48:32 -0500,
Aaron Bono <postgresql@aranya.com> wrote:
> 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.
There is a contrib package dblink that will do at least some of what you
want.
You might also see if just separating stuff into different schemas will
be good enough for you. That would allow you to have separate name spaces
but still be able to reference tables in other schemas efficiently.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hiding table structure information
2006-06-26 21:07 Re: Hiding table structure information Jonah H. Harris <jonah.harris@gmail.com>
2006-06-27 00:48 ` Re: Hiding table structure information Aaron Bono <postgresql@aranya.com>
2006-06-27 16:01 ` Re: Hiding table structure information Bruno Wolff III <bruno@wolff.to>
@ 2006-06-27 18:18 ` Aaron Bono <postgresql@aranya.com>
0 siblings, 0 replies; 6+ messages in thread
From: Aaron Bono @ 2006-06-27 18:18 UTC (permalink / raw)
To: Bruno Wolff III <bruno@wolff.to>; Aaron Bono <postgresql@aranya.com>; Jonah H. Harris <jonah.harris@gmail.com>; carlosreimer@terra.com.br; rodrigo.sakai@zanthus.com.br; pgsql-admin
>
> > 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.
>
> There is a contrib package dblink that will do at least some of what you
> want.
I will look into dblink. Thanks!
You might also see if just separating stuff into different schemas will
> be good enough for you. That would allow you to have separate name spaces
> but still be able to reference tables in other schemas efficiently.
>
Actually most of the updates will be in the same database but different
schemas as you suggest. Unfortunately, due to client requirements, not
everything will be structured that way. I may have some other options
though...
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hiding table structure information
2006-06-26 21:07 Re: Hiding table structure information Jonah H. Harris <jonah.harris@gmail.com>
2006-06-27 00:48 ` Re: Hiding table structure information Aaron Bono <postgresql@aranya.com>
@ 2006-06-28 00:31 ` Jim Nasby <jnasby@pervasive.com>
1 sibling, 0 replies; 6+ messages in thread
From: Jim Nasby @ 2006-06-28 00:31 UTC (permalink / raw)
To: Aaron Bono <postgresql@aranya.com>; +Cc: Jonah H. Harris <jonah.harris@gmail.com>; carlosreimer@terra.com.br; rodrigo.sakai@zanthus.com.br; pgsql-admin
On Jun 26, 2006, at 7:48 PM, Aaron Bono wrote:
> 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?
google: postgresql dblink
> 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.
http://gborg.org/slony1
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2006-06-28 00:31 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-06-26 17:39 Hiding table structure information Carlos H. Reimer <carlosreimer@terra.com.br>
2006-06-26 21:07 Re: Hiding table structure information Jonah H. Harris <jonah.harris@gmail.com>
2006-06-27 00:48 ` Aaron Bono <postgresql@aranya.com>
2006-06-27 16:01 ` Bruno Wolff III <bruno@wolff.to>
2006-06-27 18:18 ` Aaron Bono <postgresql@aranya.com>
2006-06-28 00:31 ` Jim Nasby <jnasby@pervasive.com>
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