|From:||Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>|
|To:||Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>|
|Cc:||Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>|
|Subject:||Re: Add support for tuple routing to foreign partitions|
|Views:||Raw Message | Whole Thread | Download mbox|
On 2017/08/17 20:37, Ashutosh Bapat wrote:
> On Thu, Aug 17, 2017 at 1:57 PM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> I spent some time on this. To handle that, I'd like to propose doing
>> something similar to \copy (frontend copy): submit a COPY query "COPY ...
>> FROM STDIN" to the remote server and route data from a file to the remote
>> server. For that, I'd like to add new FDW APIs called during CopyFrom that
>> allow us to copy to foreign tables:
> The description seems to support only COPY to a foreign table from a
> file, but probably we need the support other way round as well. This
> looks like a feature (support copy to and from a foreign table) to be
> handled by itself.
Agreed. I'll consider how to handle copy-from-a-foreign-table as well.
|Next Message||Etsuro Fujita||2017-08-17 12:00:16||Re: postgres_fdw bug in 9.6|
|Previous Message||Ashutosh Bapat||2017-08-17 11:37:12||Re: Add support for tuple routing to foreign partitions|