X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D95E29FA5FC for ; Mon, 26 Jun 2006 21:48:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 51071-09 for ; Mon, 26 Jun 2006 21:48:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 7A8559FA2F7 for ; Mon, 26 Jun 2006 21:48:34 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so2331395ugf for ; Mon, 26 Jun 2006 17:48:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=A+tughwanG8xiWw9pgVKY5aGrjeeiO5izir6Qg2mnZg/Bk5WDMNoNa6/FGa17maFw7GagHBqJFnjDLCmMIc8DNPz6XCOJKpfknnd5bwlnn9i/kvE0BjymAPONFuvESfNxiNDa2FwnhFNz+4imqBaFAIVUjt9lwsoxBoAPE9B2MA= Received: by 10.78.164.13 with SMTP id m13mr2329814hue; Mon, 26 Jun 2006 17:48:32 -0700 (PDT) Received: by 10.78.29.2 with HTTP; Mon, 26 Jun 2006 17:48:32 -0700 (PDT) Message-ID: Date: Mon, 26 Jun 2006 19:48:32 -0500 From: "Aaron Bono" To: "Jonah H. Harris" Subject: Re: Hiding table structure information Cc: carlosreimer@terra.com.br, rodrigo.sakai@zanthus.com.br, pgsql-admin@postgresql.org In-Reply-To: <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11037_26131977.1151369312777" References: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS> <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com> X-Google-Sender-Auth: 84f44f5e0f307b6f X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/250 X-Sequence-Number: 22212 ------=_Part_11037_26131977.1151369312777 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 wrote: > > On 6/26/06, Carlos H. Reimer 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/ > > ------=_Part_11037_26131977.1151369312777 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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/

------=_Part_11037_26131977.1151369312777--