From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Eric Lauzon <eric(dot)lauzon(at)abovesecurity(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Schema vs Independant Databases, ACLS,Overhead,pg_hba.conf |
Date: | 2006-02-25 16:03:00 |
Message-ID: | 20060225160300.GD4756@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Eric Lauzon wrote:
Hi,
> Now that the issue is that we can't implement a per connection user/ACL
> pair , would it be a good idea to implement
> Schema ACLS and mabey pg_hba.conf Schema acls
This is certainly possible to do using GRANT and REVOKE on the schemas;
no need to fool with pg_hba.conf. You can of course create groups/roles
to simplify the assignment of privileges, as needed.
Apart from the much more efficient queries (i.e. using cross-schema
queries instead of dblink), I don't think you're going to see much
change in performance, because most things like WAL and shared buffers
are shared among all databases anyway. You'd save a bit by not having
multiple copies of system caches (pg_class cache, etc), but I wouldn't
know if that's going to be very noticeable next to the primary
improvement.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Javier Somoza | 2006-02-27 10:03:14 | fsync and battery-backed caches |
Previous Message | Luke Lonergan | 2006-02-25 15:49:51 | Re: Reliability recommendations |