Looks like someone could take advantage of the broader range of sequence values,
but only if they explicitly created their column as int8 with the default set to
nextval('the_sequence').
Should the serial datatype be changed to create an int8, or a new serial8
datatype created that does this??
--Wes Sheldahl
Bruce Momjian <pgman%candle.pha.pa.us@interlock.lexmark.com> on 12/28/2001
01:11:33 PM
To: Tom Lane <tgl%sss.pgh.pa.us@interlock.lexmark.com>
cc: Joe Conway <joseph.conway%home.com@interlock.lexmark.com>, Justin Clift
<justin%postgresql.org@interlock.lexmark.com>, PostgreSQL General Mailing
List <pgsql-general%postgresql.org@interlock.lexmark.com> (bcc: Wesley
Sheldahl/Lex/Lexmark)
Subject: Re: [GENERAL] First decent PostgreSQL CBT now on
techdocs.postgresql.org
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I do have a question about that. If I do this:
> > test=> create table test (x serial);
> > My column is an integer.
>
> So it is. When the sequence reaches 2147483648 you'll start getting
> ERROR: int8 conversion to int4 is out of range
Uh, so what is the advantage of using int8 sequences internally? Just
the error message?
--
Bruce Momjian | http://candle.pha.pa.us