| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | ashutosh(dot)bapat(at)enterprisedb(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Async execution of postgres_fdw. |
| Date: | 2015-01-14 08:24:50 |
| Message-ID: | 20150114.172450.102338109.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
> - The issue of PREPARE is not addressed yet.
...
> > In case of Prepared statements, ExecInit is called at the end of planning,
> > without subsequent execution like the case of EXPLAIN. I see that the patch
> > handles EXPLAIN well, but I didn't see any specific code for PREPARE.
>
> I'll look into the case after this, but I'd like to send a
> revised patch at this point.
Mmm.. CreateExecutorState() looks to be called when calculating
the expression in predicates, clauses, or EXECUTE parameters. All
of these complete SQL execution if any. And I couldn't make the
situation you mentioned.
Could you give me an example or illustration about such a
situation where ExecInit alone is called without
IterateForeignScan?
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2015-01-14 08:43:25 | Re: INSERT ... ON CONFLICT UPDATE and RLS |
| Previous Message | Michael Paquier | 2015-01-14 07:55:58 | Typo fix in alter_table.sgml |