| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |
| Date: | 2019-04-24 13:25:04 |
| Message-ID: | CANP8+jJ=8y22CqTF8x9fxnLpV3hDH_7Vpw43T4BTJWJKCxRGeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, 24 Apr 2019 at 12:55, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-04-24 13:26:59 | pgsql: Unify error messages |
| Previous Message | Laurenz Albe | 2019-04-24 13:04:47 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-04-24 13:25:12 | Re: finding changed blocks using WAL scanning |
| Previous Message | Laurenz Albe | 2019-04-24 13:04:47 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |