Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> On 25.05.2011 17:47, Tom Lane wrote:
>> [ scratches head ... ] Why does the save/restore in ExecEvalCase not
>> take care of this?
> The mistake happens during planning, when the SQL function is inlined
> and pre-evaluated.
Hm. I'm inclined to think this may be more of a bug in the inlining
process than anything else. I have to run off for a doctor's
appointment, but will look at this closer later today.
regards, tom lane