| From: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
|---|---|
| To: | 'Craig Ringer' <craig(dot)ringer(at)enterprisedb(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | RE: POC: postgres_fdw insert batching |
| Date: | 2020-11-25 06:31:53 |
| Message-ID: | TYAPR01MB2990FC82356124F692545B53FEFA0@TYAPR01MB2990.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
> I suggest that when developing this, you keep in mind the ongoing work on the libpq pipelining/batching enhancements, and also the way many interfaces to foreign data sources support asynchronous, concurrent operations.
Yes, thank you, I bear it in mind. I understand it's a feature for batching multiple kinds of SQL statements like DBC's batch updates.
> I'd argue it's pretty much vital for decent performance when talking to a cloud database from an on-prem server for example, or any other time that round-trip-time reduction is important.
Yeah, I'm thinking of the data migration and integration as the prominent use case.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seino Yuki | 2020-11-25 06:40:36 | Re: [PATCH] Add features to pg_stat_statements |
| Previous Message | Pavel Stehule | 2020-11-25 06:19:56 | Re: [Proposal] Global temporary tables |