| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Asynchronous execution on FDW |
| Date: | 2015-07-03 20:41:48 |
| Message-ID: | 5596F38C.2090900@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/02/2015 08:48 AM, Kyotaro HORIGUCHI wrote:
> - It was a problem when to give the first kick for async exec. It
> is not in ExecInit phase, and ExecProc phase does not fit,
> too. An extra phase ExecPreProc or something is too
> invasive. So I tried "pre-exec callback".
>
> Any init-node can register callbacks on their turn, then the
> registerd callbacks are called just before ExecProc phase in
> executor. The first patch adds functions and structs to enable
> this.
At a quick glance, I think this has all the same problems as starting
the execution at ExecInit phase. The correct way to do this is to kick
off the queries in the first IterateForeignScan() call. You said that
"ExecProc phase does not fit" - why not?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan de Visser | 2015-07-03 20:47:13 | Re: Idea: closing the loop for "pg_ctl reload" |
| Previous Message | Tom Lane | 2015-07-03 20:05:17 | Re: WAL logging problem in 9.4.3? |