Re: Not representable result out of too large range - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Not representable result out of too large range
Date
Msg-id 24333.997128131@sss.pgh.pa.us
Whole thread Raw
In response to Not representable result out of too large range  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> We have five different expected files for the int2 and int4 tests because
> every system has a different idea on what to print for ERANGE.  I'm about
> to add another version.  Would it make more sense to hard code one wording
> and not use strerror here?

Kinda sounds like the path of least resistance, doesn't it?  I assume
you'd do the substitution inside elog(), so it's consistent for all
places that might report ERANGE via %m ?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible solution for LIKE optimization
Next
From: Tom Lane
Date:
Subject: Notes about int8 sequences