DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=KneIg2J9oMIEdO0sTE29ntROvy+pHfOMsQs9yzSi49G88DDWgrscAtiaGEbCUznu+j
	Vm6Bisz0YULhGHUyGfdiWN3qETYsp2w4vV+9bM8V6XPaZofHSEjRwubl4s4snovxjk1T
	/OWojFOnnpnRtogNKwHERhJvJJFAc9gItVcMI=
MIME-Version: 1.0
In-Reply-To: <20100622230754.GE15203@fetter.org>
References: <4C207403.3080103@gmail.com>
	<AANLkTikX89l8iqkpcAJvxlJl5fP7dvyhmrHU8oer-lfY@mail.gmail.com>
	<20100622230754.GE15203@fetter.org>
From: Thom Brown <thombrown@gmail.com>
Date: Wed, 23 Jun 2010 00:16:06 +0100
Message-ID: <AANLkTilfZooZpo_GqnAZHE9e_yk_KhVOmpU1AT-V-WW_@mail.gmail.com>
Subject: Re: INTEGER range ("-2147483648" is not accepted.)
To: David Fetter <david@fetter.org>
Cc: Satoshi Nagayasu <satoshi.nagayasu@gmail.com>, pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 23 June 2010 00:07, David Fetter <david@fetter.org> wrote:
> On Tue, Jun 22, 2010 at 09:36:30AM +0100, Thom Brown wrote:
>> 2010/6/22 Satoshi Nagayasu <satoshi.nagayasu@gmail.com>:
>> > Hi all,
>> >
>> > I've found a bit strange thing on the INTEGER range in the official ma=
nual.
>> >
>> > http://www.postgresql.org/docs/8.4/interactive/datatype-numeric.html
>> >
>> > According to the official manual, the INTEGER range is "-2147483648 to=
 +2147483647".
>> > However, my example in below shows that "-2147483648" is not accepted.
>> >
>> > Is this correct? Any suggestions?
>> >
>> > Regards,
>> >
>> > ---------------------------------------------------------------------
>> > template1=3D# SELECT version();
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0version
>> > ----------------------------------------------------------------------=
--------------------------------------
>> > =A0PostgreSQL 8.4.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.=
1.2 20071124 (Red Hat 4.1.2-42), 32-bit
>> > (1 row)
>> >
>> > template1=3D# SELECT -2147483647::integer;
>> > =A0?column?
>> > -------------
>> > =A0-2147483647
>> > (1 row)
>> >
>> > template1=3D# SELECT -2147483648::integer;
>> > ERROR: =A0integer out of range
>> > template1=3D# SELECT +2147483648::integer;
>> > ERROR: =A0integer out of range
>> > template1=3D# SELECT +2147483647::integer;
>> > =A0?column?
>> > ------------
>> > =A02147483647
>> > (1 row)
>> >
>> > template1=3D#
>> > ---------------------------------------------------------------------
>> >
>>
>> Hmm... yes, that's not what I'd expect either:
>>
>> postgres=3D# SELECT -32768::smallint;
>> ERROR: =A0smallint out of range
>> postgres=3D# SELECT -9223372036854775808::bigint;
>> ERROR: =A0bigint out of range
>>
>> I think those min values are all out by 1.
>
> Nope. =A0Same problem.
>
> SELECT (-32768)::smallint;
> =A0-32768
>
> SELECT (-9223372036854775808)::bigint;
> =A0-9223372036854775808
>
> I agree that the appropriate error message should complain about the
> actual error, which is that 32768, or 2147483648, or
> 9223372036854775808, as the case may be, is out of range in the
> positive direction. =A0Possibly the "hint" might mention that :: binds
> tighter than - does.
>

Is that the right behaviour though?  Shouldn't the signed value reach
the cast step rather than the absolute value?  Or maybe Postgres could
implicitly accept -12345::integer to be (-12345)::integer.  Is there a
blocking reason as to why it must work this way?  Am I asking too many
questions?  Was that last question necessary?

Thom