Re: Changing the concept of a DATABASE

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing the concept of a DATABASE
Date: 2012-05-22 17:18:41
Message-ID: 4FBBCA71.3080505@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2012-05-22 17:24:35 Add primary key/unique constraint using prefix columns of an index
Previous Message David Fetter 2012-05-22 17:15:33 Re: How could we make it simple to access the log as a table?