| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Luis Carril <luis(dot)carril(at)swarm64(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PG Bug reporting form <noreply(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |
| Date: | 2018-12-19 07:50:55 |
| Message-ID: | 5C19F85F.1040909@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
(2018/12/19 13:04), Michael Paquier wrote:
> On Wed, Dec 19, 2018 at 01:01:01PM +0900, Amit Langote wrote:
>> It may happen sooner that you may think. :)
>>
>> Currently, COPY into foreign tables uses APIs used by INSERT, so one row
>> at a time interface. It'd certainly be better to allow FDWs to be able to
>> do bulk transfer. I think Fujita-san has said he wants to work on that:
>>
>> https://www.postgresql.org/message-id/5AB4F190.1000804%40lab.ntt.co.jp
>
> That's interesting.
Thanks! Actually, I (re-)started working on that from this week. (Not
sure whether I can post a patch for that before the next CF.)
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-12-19 08:34:22 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |
| Previous Message | Etsuro Fujita | 2018-12-19 07:49:19 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |