Andres Freund <andres@anarazel.de> writes:
> On 2018-10-26 08:02:59 +0200, Fabien COELHO wrote:
>> The error message may be nicer by expliciting the offending string, and/or
>> locating it precisely within the query?
> Including the string would make the function not leak proof though, so
> that seems like a no-go. Location would be possible, but there's some
> architectural issues around doing so at execution time - we only really
> have the setup to do so at parse time currently. Tom was looking to
> change that at some point however, iirc.
Yeah. That project was on hold till you got done whacking expression
execution around; but if that's about finished, I might take another look.
regards, tom lane
