| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Refactor parse analysis of EXECUTE command |
| Date: | 2019-11-08 12:34:40 |
| Message-ID: | 6a9d20c5-fa8e-97fc-b548-8bac3883f57c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-11-08 09:03, Pavel Stehule wrote:
> Parse analysis of EXECUTE does not access any tables, so if I
> understood
> this correctly, this concern doesn't apply here.
>
>
> it should not be true - the subquery can be a expression.
Arguments of EXECUTE cannot be subqueries.
> Minimally on SQL level is not possible do prepare on execute. So execute
> should be evaluate as one step.
Well, that's kind of the question that is being discussed in this thread.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2019-11-08 12:43:12 | Re: Global temporary tables |
| Previous Message | Pavel Stehule | 2019-11-08 11:26:55 | Re: dropdb --force |