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

From Tom Lane
Subject Re: BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type
Date
Msg-id 19374.1393484563@sss.pgh.pa.us
Whole thread Raw
In response to BUG #9366: Default MAXVALUE is incorrect for sequence object of serial type  (kashi@fhpg.net)
List pgsql-bugs
kashi@fhpg.net writes:
> 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.

This is not a bug, but intentional behavior.  See

http://www.postgresql.org/message-id/flat/E1VeK8A-0006V4-EX@wrigleys.postgresql.org#E1VeK8A-0006V4-EX@wrigleys.postgresql.org

> 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".

So?  If we set the sequence limit differently, the case would still fail,
just with a different error message.  And you'd then have two things to
fix, not only one, to get your database back in working order.

            regards, tom lane

pgsql-bugs by date:

Previous
From: digoal@126.com
Date:
Subject: BUG #9364: why pg_user_mappings can query by nonsuperuser?
Next
From: Rainer Tammer
Date:
Subject: Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1