Re: Changing the concept of a DATABASE

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing the concept of a DATABASE
Date: 2012-05-22 22:26:08
Message-ID: 4FBC1280.1060804@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> That's only true if you try to satisfy both goals at once, which I'm
> not suggesting. So I believe that proposition to be false.

Oh, ok. Per your original email and follow-up arguments, you seemed to
be doing just that.

>> An alternative idea -- and one which could be deployed a lot faster --
>> is to come up with a tool which makes it easy to migrate an entire
>> database into a separate schema or set of schemas in an existing
>> database. And improvements to manage schema visility/path better, I
>> suppose.
>
> Yes, it is possible to improve things there also.

Feh, and nested schema, for that matter. So, there's a fair bit of work
wherever we bite it off.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2012-05-22 23:10:21 Proposal: add new field to ErrorResponse and NoticeResponse
Previous Message Josh Berkus 2012-05-22 22:21:52 Re: Per-Database Roles