Pavel Stehule <pavel.stehule@gmail.com> writes: > personally I prefer syntax without FOR keyword - because following keyword > must be reserved keyword
> SET x = .., y = .. SELECT ... ;
Nope. Most of the statement-starting keywords are *not* fully reserved; they don't need to be as long as they lead off the statement. But this proposal would break that. We need to put FOR or IN or another already-fully-reserved keyword after the SET list, or something's going to bite us.
the possibility to control plan cache for any command via GUC outside PLpgSQL can introduce lot of question.
What impact will be on PREPARE command and on EXECUTE command?
If we disable plan cache for EXECUTE, should we remove plan from plan cache? ...
Can we have some diagnostic to get info if some command has cached plan or not?
