BUG #1526: SHRT_MIN out of range on explicit type conversion

From: "Kelly Burkhart" <pgkrb(at)kkcsm(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1526: SHRT_MIN out of range on explicit type conversion
Date: 2005-03-04 20:14:06
Message-ID: 20050304201406.BF74DF176F@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1526
Logged by: Kelly Burkhart
Email address: pgkrb(at)kkcsm(dot)net
PostgreSQL version: 7.4.2
Operating system: SuSE Linux 9.1 i386 & x86-64
Description: SHRT_MIN out of range on explicit type conversion
Details:

An explicit type conversion of an integer constant representing the minimum
value that type can hold results in an 'integer out of range' error.

From psql, the following will fail:

select -32768::int2;
select -2147483648::int4;
select -9223372036854775808::int8;

If the constants are strings, there is no failure. For instance the
following will succeed:

select '-32768'::int2;
select '-2147483648'::int4;
select '-9223372036854775808'::int8;

Also increasing the value by one does not result in failure. The following
will succeed:

select -32767::int2;
select -2147483647::int4;
select -9223372036854775807::int8;

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Theo Petersen 2005-03-04 20:22:13 BUG #1527: select retrieves 0 rows after vacuum analyze
Previous Message Sergio Lob 2005-03-04 13:58:20 Re: BUG #1523: precision column value returned from getTypeInfo()