Postgres Pro
Downloads
Home   >   mailing lists

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

From Simon Riggs
Subject Re: pgsql: Allow insert and update tuple routing and COPY for foreign table
Date
Msg-id CANP8+jJ=8y22CqTF8x9fxnLpV3hDH_7Vpw43T4BTJWJKCxRGeA@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Allow insert and update tuple routing and COPY for foreigntable  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
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
Tree view
On Wed, 24 Apr 2019 at 12:55, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote:
 
> My point is that this should not be necessary.

In my opinion, I think this is necessary...

Could we decide by looking at what FDWs are known to exist?  I hope we are trying to avoid breakage in the smallest number of FDWs.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-committers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: pgsql: Allow insert and update tuple routing and COPY forforeign table
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Unify error messages