| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Manuel Kniep <m(dot)kniep(at)web(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, "fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: foreign table batch inserts |
| Date: | 2016-05-19 13:07:09 |
| Message-ID: | CAMsr+YHBenGv-qNMRSdBJ+skV+868edHum1TEv+n72ywyNz67w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 May 2016 at 14:08, Tsunakawa, Takayuki <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com
> wrote:
>
>
> Yes, I want FE-BE protocol-level batch inserts/updates/deletes, too. I
> was just about to start thinking of how to implement it because of recent
> user question in pgsql-odbc. The OP uses Microsoft SQL Server Integration
> Service (SSIS) to migrate data to PostgreSQL. He asked for a method to
> speed up multi-row inserts, because the ODBC's multi-row insert API takes
> as long a time as when performing single-row inserts separately. This may
> prevent the migration to PostgreSQL.
>
Well, there's FE/BE level batching/pipelining already. Just no access to it
from libpq.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2016-05-19 14:14:31 | Re: Autovacuum to prevent wraparound tries to consume xid |
| Previous Message | Amit Langote | 2016-05-19 10:29:33 | Re: Declarative partitioning |