Re: FOREIGN TABLE doc fix

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Shigeru Hanada <hanada(at)metrosystems(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FOREIGN TABLE doc fix
Date: 2011-06-13 15:38:49
Message-ID: 4DF62F09.4060004@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/13/2011 10:25 AM, Dave Page wrote:
>
>> Don't hold your breath. We'll probably be making enough changes in the
>> FDW infrastructure (particularly planner support) that making an FDW
>> work on both 9.1 and 9.2 would be an exercise in frustration, if it's
>> even possible.
> Oh joy. There's a GSoC student working on 2 non-trivial FDW's right
> now, and I have a couple I've been working on. If we're going to make
> the API incompatible to that extent, we might as well not bother :-(
>

If nobody bothers then there won't be any experience on which to base a
stable API. In particular, I think it's crucial that we get working FDWs
for MySQL, SQLServer and Oracle ASAP.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2011-06-13 15:38:51 Re: procpid?
Previous Message Alvaro Herrera 2011-06-13 15:37:58 Re: wrong message on REASSIGN OWNED