| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, elprans(at)gmail(dot)com, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15458: pg_typeof inconsistency on negative integer constant limits |
| Date: | 2018-10-26 08:17:38 |
| Message-ID: | 23665.1540541858@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-10-26 09:31:18 | BUG #15460: Error while creating index or constraint |
| Previous Message | Andres Freund | 2018-10-26 06:24:30 | Re: BUG #15458: pg_typeof inconsistency on negative integer constant limits |