Re: BUG #14986: -2147483648 is minimum value of integer but -2147483648::integer fails (out of range).

From: Greg Stark <stark(at)mit(dot)edu>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, binoternary(at)gmail(dot)com, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14986: -2147483648 is minimum value of integer but -2147483648::integer fails (out of range).
Date: 2017-12-21 21:18:05
Message-ID: CAM-w4HMUwZZZxD7dogCQnNXU_0YC-wkDYOfxz=83vR1tiZrEjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 21 December 2017 at 14:13, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2017-12-21 14:05:07 +0000, Greg Stark wrote:
>> I wonder why the "out of range" error doesn't print the actual value
>> it's trying to cast. That would help the user here...
>
> We'd have to mark it as non-leakproof in that case.

Damn that's annoying.

But..... uh, isn't it already leaking that the value is not in 99.99999998% of
the bigint range?

--
greg

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2017-12-21 21:26:23 BUG #14991: postgis-2.4.so: undefined symbol: GEOSMinimumClearance
Previous Message Todd A. Cook 2017-12-21 17:53:57 Re: BUG #14990: hashint4() <> hashint8() for small negative values, causing hash joins to fail