BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type - Mailing list pgsql-bugs

From kashi@fhpg.net
Subject BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type
Date
Msg-id 20140227034510.26578.68200@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      9366
Logged by:          KASHI, Yukihito
Email address:      kashi@fhpg.net
PostgreSQL version: 9.1.6
Operating system:   Windows7 / Linux version 2.6.18
Description:

When I create the new table as serial type column , I found a strange
condition on sequence parameter.
It could be specified as integer, but MAXVALUE of sequence is set as
Bigint.

ex)
CREATE TABLE test_int (seq_int serial, test_int integer);
At that case, MAXVALUE of test_int_seq_int_seq is "9223372036854775807". As
the result, if the current value is 2147483647, next insert operation could
be failed as "ERROR: integer out of range".

I briefly check the release note, but I couldn't find any changes related
with serial between 9.1.7 - 9.1.12.

Thank you.

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #9342: CPU / Memory Run-away
Next
From: Patrick Wege
Date:
Subject: Re: BUG #9308: The application failed to initialize properly