From: | Darren Duncan <darren(at)darrenduncan(dot)net> |
---|---|
To: | rod(at)iol(dot)ie |
Cc: | Condor <condor(at)stz-bg(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Two databases on the same server, looking for idea how to restrict access. |
Date: | 2012-06-08 04:03:26 |
Message-ID: | 4FD1798E.3000205@darrenduncan.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Raymond O'Donnell wrote:
> On 07/06/2012 15:39, Condor wrote:
>> I have two databases on postgresql in different servers, one main
>> database and one secondary not much important,
>> but the problem is they should use some tables both for reading and
>> writing and the secondary postgresql should not
>> have access to whole database on the main database. Im thinking to
>> combine both databases on same server and split them
>> with different schema also to make load balance and some kind of
>> permissions to restrict secondary database to read whole
>> database on the main database or some kind of shared tables (files). Any
>> one have some ideas how I can do this ? Any ideas is welcome.
>
> Your idea of two schemas in the one database is the way to go - you
> cannot share tables between different databases.
Further to this point, make sure you have a different database user for each of
the people or applications you want to service, give the two schemas different
owners or do appropriate privilege granting in the database, to keep each
person/application to just the things they should see and nothing else. --
Darren Duncan
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-06-08 05:34:50 | Re: Postgres 9.2 beta2 one-click installer on windows |
Previous Message | Zenaan Harkness | 2012-06-08 01:08:37 | Re: Procedural Languages |