Corey Huinker <corey.huin...@gmail.com> writes: > My not-ready-for-16 work on CAST( ... ON DEFAULT ... ) involved making > FuncExpr/IoCoerceExpr/ArrayCoerceExpr have a safe_mode flag, and that > necessitates adding a reserror boolean to ExprEvalStep for subsequent steps > to test if the error happened.
Why do you want it in ExprEvalStep ... couldn't it be in ExprState?
I can't see why you'd need more than one at a time during evaluation.
regards, tom lane
