Skip site navigation (1) Skip section navigation (2)

Re: What are the advantages of not being able to access multiple databases with one connection?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: crocket <crockabiscuit(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: What are the advantages of not being able to access multiple databases with one connection?
Date: 2012-11-05 17:33:05
Message-ID: CA+TgmoYo8gpX8Q101zOOKMg3gnQyzhpheX_cd-Hxy2fvqk5gZw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Oct 30, 2012 at 8:37 AM, crocket <crockabiscuit(at)gmail(dot)com> wrote:
> MySQL permits a connection to access multiple databases.
> But Postgresql restricts a connection to one database.
> I think postgresql database connection is somewhat limited.
>
> Is it an old and decrepit design? or does it deserve some appreciations?

I think it deserves some appreciation.  Each database is completely
isolated in terms of privileges, which is sometimes useful.  Also, if
you somehow manage to fry the system catalogs in one database, the
other ones can still survive.  The role played by databases in MySQL
is served by schemas in PostgreSQL, so I don't see that there is a
functional gap here.  I am not sure I'd bother implementing the
multi-database concept today if we didn't have it already ... but it
seems kind of pointless to rip it out given that it's already there.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-11-05 17:35:54
Subject: Re: [PATCH] PL/Python: Add spidata to all spiexceptions
Previous:From: John R PierceDate: 2012-11-05 17:30:30
Subject: Re: [PERFORM] out of memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group