Re: Usability or Data Bug in SERIAL column declarations - Mailing list pgsql-bugs

From elein
Subject Re: Usability or Data Bug in SERIAL column declarations
Date
Msg-id 20041027175409.J8064@cookie.varlena.com
Whole thread Raw
In response to Re: Usability or Data Bug in SERIAL column declarations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Usability or Data Bug in SERIAL column declarations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
But shouldn't it wrap when it hits the max?
Assuming wrapping is an OK behavior, not setting
a proper max will eliminate that option for overflow.

--elein


On Wed, Oct 27, 2004 at 08:30:37PM -0400, Tom Lane wrote:
> elein <elein@varlena.com> writes:
> > In both cases sequences are created as int8 values with
> > a maximum of 9223372036854775807.
>
> > BUG: The assignment of the table containing the int4 column
> > will overflow at 2147483648 (max integer size).
>
> I don't think this is really a problem.
>
> You are going to have errors when you run out of int4-sized identifiers
> in either case.  If we reduce the sequence's maximum, that just means
> one more thing you'll have to fix in order to recover.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Usability or Data Bug in SERIAL column declarations
Next
From: Tom Lane
Date:
Subject: Re: Usability or Data Bug in SERIAL column declarations