| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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 15:20:46 |
| Message-ID: | CAFj8pRAG6EiRZG7djmQ6DfqSHJ9789zs7MzXEgz2+BV3TMfgfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pá 8. 11. 2019 v 13:34 odesílatel Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> napsal:
> 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.
>
ok
>
> > 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.
>
I say it not cleanly - I think so this change should be safe, because
parsing, transforming, and execution must be in one statement.
Regards
Pavel
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-11-08 15:50:16 | Re: Why overhead of SPI is so large? |
| Previous Message | Christoph Berg | 2019-11-08 15:12:22 | Re: Monitoring disk space from within the server |