Re: pgsql: Allow insert and update tuple routing and COPY for foreign table

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, pgsql-committers <pgsql-committers@lists.postgresql.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-22T20:24:15Z
Lists: pgsql-hackers
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



Commits

  1. Add FDW documentation notes about insert and update tuple routing and COPY.

  2. Allow insert and update tuple routing and COPY for foreign tables.