Re: [HACKERS] Add support for tuple routing to foreign partitions
От | Etsuro Fujita |
---|---|
Тема | Re: [HACKERS] Add support for tuple routing to foreign partitions |
Дата | |
Msg-id | de0b7579-7a4d-b5a8-88ff-b01b6776a1c5@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] Add support for tuple routing to foreign partitions (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] Add support for tuple routing to foreign partitions
|
Список | pgsql-hackers |
On 2017/08/19 2:12, Robert Haas wrote: > On Thu, Aug 17, 2017 at 4:27 AM, Etsuro Fujita > <fujita.etsuro@lab.ntt.co.jp> wrote: >> I think that would be much more efficient than INSERTing tuples into the >> remote server one by one. What do you think about that? > > I agree, but I wonder if we ought to make it work first using the > existing APIs and then add these new APIs as an optimization. I'm not sure that's a good idea because that once we support INSERT tuple-routing for foreign partitions, we would have a workaround: INSERT INTO partitioned_table SELECT * from data_table where data_table is a foreign table defined for an input file using file_fdw. > postgres_fdw isn't the only FDW in the world, and it's better if > getting a working implementation doesn't require too many interfaces. Agreed. My vote would be to leave the COPY part as-is until we have these new APIs. Best regards, Etsuro Fujita
В списке pgsql-hackers по дате отправления: