BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type

From: kashi(at)fhpg(dot)net
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type
Date: 2014-02-27 03:45:10
Message-ID: 20140227034510.26578.68200@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 9366
Logged by: KASHI, Yukihito
Email address: kashi(at)fhpg(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-02-27 07:02:43 Re: BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type
Previous Message digoal 2014-02-27 02:07:35 BUG #9364: why pg_user_mappings can query by nonsuperuser?