Re: pgsql: Allow insert and update tuple routing and COPY for foreign table - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Allow insert and update tuple routing and COPY for foreign table
Date
Msg-id CA+TgmoaAcNNpNO41yYu1afo1k3t9YoCd0LweYLthyo9LLHp_Ag@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Allow insert and update tuple routing and COPY forforeign table  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: pgsql: Allow insert and update tuple routing and COPY forforeign table  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: pgsql: Allow insert and update tuple routing and COPY forforeign table  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-committers
On Mon, Apr 22, 2019 at 3:37 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> Sure, it is not hard to modify a FDW to continue working with v11.
>
> My point is that this should not be necessary.

I'm not sure whether this proposal is a good idea or a bad idea, but I
think that it's inevitable that FDWs are going to need some updating
for new releases as the API evolves.  That has happened before and
will continue to happen.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-committers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: pgsql: Allow insert and update tuple routing and COPY forforeign table
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Allow insert and update tuple routing and COPY forforeign table