> 1. Ability to have a Role that can only access one Database > > 2. Allow user info to be dumped with a database, to make a db > completely self-consistent > > 3. Allow databases to be transportable > > 4. Allow users to access tables in >1 database easily, with appropriate > rights.
The last requirement seems completely contradictory to the other three. Either we're trying to make databases even more isolated as multi-tenant Catalogs, or we're not. Trying to do both at the same time is failure-by-design. Given that we offer schema as an alternative to multiple databases, and users are starting to get used to them, I think that requirement (4) is just a bad idea, and not worth pursuing, except in the context of pgsql_fdw. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers