Re: Changing the concept of a DATABASE

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing the concept of a DATABASE
Date: 2012-05-22 17:43:11
Message-ID: CA+U5nMJYXG2B73Sx-SQ+k-uiwSq6sXcRTtjQFW5j-9cKtF=XaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22 May 2012 18:35, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> If I have a customer with 1 database per user, how do they run a query
>> against 100 user tables? It would require 100 connections to the
>> database. Doing that would require roughly x100 the planning time and
>> x100 the connection delay. Larger SQL statements pass their results
>> between executor steps using libpq rather than direct calls.
>
> Why is this hypothetical customer using separate databases?  This really
> seems like a case of "doctor, it hurts when I do this".

Databases are great for separating things, but sometimes you want to
un-separate them in a practical way.

I'm surprised that you're so negative about an ease of use feature. I
had understood you cared about fixing problems experienced by our
developers.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-05-22 17:51:16 Re: Changing the concept of a DATABASE
Previous Message Tom Lane 2012-05-22 17:41:00 Re: Add primary key/unique constraint using prefix columns of an index