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 98DD19FA437 for ; Tue, 27 Jun 2006 15:18:29 -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 13498-01 for ; Tue, 27 Jun 2006 15:18:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by postgresql.org (Postfix) with ESMTP id 0174B9FA10A for ; Tue, 27 Jun 2006 15:18:19 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so2740328ugf for ; Tue, 27 Jun 2006 11:18:18 -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:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=k51It3rfjKkOP9Q9PwoDNFbyzBj4tJYuM+tZfqPrhMsIkyKh+9LJ2Wv9/QTRG2Bd2kDhJ3kr/1K4Jy8QTkgh4rYjAN+lSYdX4EA3kloP/oUIB/5yRUt6kz3sG7Bl32Sk1L7349vqjCK19wlYekzcZuiBXjpGQewE7s0E0GnOTZ4= Received: by 10.78.179.12 with SMTP id b12mr2611050huf; Tue, 27 Jun 2006 11:18:18 -0700 (PDT) Received: by 10.78.29.2 with HTTP; Tue, 27 Jun 2006 11:18:18 -0700 (PDT) Message-ID: Date: Tue, 27 Jun 2006 13:18:18 -0500 From: "Aaron Bono" To: "Bruno Wolff III" , "Aaron Bono" , "Jonah H. Harris" , carlosreimer@terra.com.br, rodrigo.sakai@zanthus.com.br, pgsql-admin@postgresql.org Subject: Re: Hiding table structure information In-Reply-To: <20060627160148.GA7623@wolff.to> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25346_30192050.1151432298347" References: <000301c6995b$7d5c9150$4700a8c0@TREEZANTHUS> <36e682920606261407i69287262n4942f7c9642f552e@mail.gmail.com> <20060627160148.GA7623@wolff.to> X-Google-Sender-Auth: 1b4132e40e81aa02 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/262 X-Sequence-Number: 22224 ------=_Part_25346_30192050.1151432298347 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. > > 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... ------=_Part_25346_30192050.1151432298347 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.

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...
------=_Part_25346_30192050.1151432298347--