| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| 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-22 00:01:40 |
| Message-ID: | CC7D554D-9648-43D2-9391-5564A696304E@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On December 21, 2017 10:18:05 PM GMT+01:00, Greg Stark <stark(at)mit(dot)edu> wrote:
>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?
Most of the relevant operations have more than one operand, or are aggregates. Especially for actually relevant data ranges. But yes, this is a way to analyze data, we knew that when adding RLS.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-12-22 01:33:56 | Re: BUG #14986: -2147483648 is minimum value of integer but -2147483648::integer fails (out of range). |
| Previous Message | PG Bug reporting form | 2017-12-21 21:26:23 | BUG #14991: postgis-2.4.so: undefined symbol: GEOSMinimumClearance |