From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | a(dot)lepikhov(at)postgrespro(dot)ru |
Cc: | etsuro(dot)fujita(at)gmail(dot)com, movead(dot)li(at)highgo(dot)ca, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Asynchronous Append on postgres_fdw nodes. |
Date: | 2020-07-02 02:14:48 |
Message-ID: | 20200702.111448.2019475770338322857.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello.
As the result of a discussion with Fujita-san off-list, I'm going to
hold off development until he decides whether mine or Thomas' is
better.
However, I fixed two misbehaviors and rebased.
A. It runs ordered Append asynchronously, but that leads to a bogus
result. I taught create_append_plan not to make subnodes async when
pathkey is not NIL.
B. It calculated the total cost of Append by summing up total costs of
all subnodes including async subnodes. It is too pessimistic so I
changed that to the following.
Max(total cost of sync subnodes, maximum cost of async subnodes);
However this is a bit too optimistic in that it ignores interference
between async subnodes, it is more realistic in the cases where the
subnode ForeignScans are connecting to different servers.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
v5-0001-Allow-wait-event-set-to-be-registered-to-resource.patch | text/x-patch | 9.3 KB |
v5-0002-Infrastructure-for-asynchronous-execution.patch | text/x-patch | 50.4 KB |
v5-0003-async-postgres_fdw.patch | text/x-patch | 58.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2020-07-02 02:46:37 | Re: estimation problems for DISTINCT ON with FDW |
Previous Message | michael | 2020-07-02 01:58:52 | Re: A patch for get origin from commit_ts. |