Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> This works well enough for regular DML statements, but it falls down for
> EXPLAIN which is a utility statement, because *parse analysis of utility
> statements doesn't do anything*. EXPLAIN actually does the parse
> analysis of its contained statement at the beginning of execution.
> And that is too late, in the scenario Pavel exhibited. Why is it too
> late? Because SPI_cursor_open_internal() intentionally "freezes" the
> ParamListInfo struct after doing initial parsing: what it copies into
> the cursor portal is just a static list of data values without the
> parser hooks (see copyParamList).
Would it make any sense for this function to get to call the hook in the
case a utility statement is being processed?
In response to
pgsql-hackers by date
|Next:||From: Dimitri Fontaine||Date: 2010-01-14 19:36:07|
|Subject: Re: Streaming replication, retrying from archive|
|Previous:||From: David Fetter||Date: 2010-01-14 18:55:16|
|Subject: Re: Miscellaneous changes to plperl [PATCH]|