Re: Changing the concept of a DATABASE - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Changing the concept of a DATABASE
Date
Msg-id 4FBB8936.9000402@dunslane.net
Whole thread Raw
In response to Re: Changing the concept of a DATABASE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Changing the concept of a DATABASE
List pgsql-hackers

On 05/22/2012 07:56 AM, Robert Haas wrote:
> On Tue, May 22, 2012 at 7:35 AM, Florian Pflug<fgp@phlo.org>  wrote:
>>> * Allow users to access tables in>1 database easily, with appropriate rights.
>> That one I'm very sceptical about. In the long run, I think we want better
>> separation of databases, not less, and this requirement carries a huge risk
>> of standing in the way of that. Also, I think that once we integrate the postgres
>> FDW into core (that's the plan in the long run, right?), we're going to get
>> a good approximation of that essentially for free.
> +1.



That seems to be leaving aside the fact that we don't currently have any 
notion of how to allow FDWs to write the foreign tables.

What is more, isn't the postgres FDW about talking to any postgres 
source? If so, does it have special smarts for when we are talking to 
ourselves? And if it doesn't then it seems unlikely to be an acceptable 
substitute for allowing talking direct to a sibling database.

I'm not at all yet sold on Simon's plan, but I'm skeptical that an FDW 
would adequately meet the case if we wanted to go that way.

cheers

andrew


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Getting rid of cheap-startup-cost paths earlier
Next
From: Robert Haas
Date:
Subject: Re: heap metapages