Re: Changing the concept of a DATABASE

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing the concept of a DATABASE
Date: 2012-05-22 12:40:22
Message-ID: 4FBB8936.9000402@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/22/2012 07:56 AM, Robert Haas wrote:
> On Tue, May 22, 2012 at 7:35 AM, Florian Pflug<fgp(at)phlo(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-05-22 12:52:08 Re: heap metapages
Previous Message Robert Haas 2012-05-22 12:29:48 Re: Getting rid of cheap-startup-cost paths earlier