| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, 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-22 20:24:15 |
| Message-ID: | CA+TgmoaAcNNpNO41yYu1afo1k3t9YoCd0LweYLthyo9LLHp_Ag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Apr 22, 2019 at 3:37 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-04-22 20:27:03 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |
| Previous Message | Laurenz Albe | 2019-04-22 19:37:25 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-04-22 20:27:03 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |
| Previous Message | Robert Haas | 2019-04-22 20:21:29 | Re: pg_dump is broken for partition tablespaces |