From: | Dave Johansen <davejohansen(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3668: type error in serial |
Date: | 2012-08-29 23:38:27 |
Message-ID: | 5a4b25cd-3398-4b5c-90a6-9788b4957bdd@googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wednesday, October 10, 2007 2:32:17 PM UTC-7, Tom Lane wrote:
> "Eric Weimer" <eweimer(at)thelocalphonecompany(dot)net> writes:
> > Creating a table with a column of type serial causes the creation of a
> > sequence tied as the default value for the column.
> > The actual type of the column is integer, however the sequence created is of
> > type bigint. If the sequence is created as a bigint, then the column should
> > also be defined as bigint.
>
> This is not a bug, primarily because we have only one size of sequence.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
I believe that the SERIAL type should set the MAXVALUE appropriately (that of a 32 bit number) because then it could give an error like "reached maximum value of sequence" rather than having people beating their heads against the wall because they can't figure out why they're getting an error of "integer out of range". That seems like a relatively minor change that could save people a LOT of headache.
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-08-30 01:23:17 | Re: PostGreSQL pgdac - C++ Builder 2007 |
Previous Message | daniel | 2012-08-29 21:36:38 | BUG #7510: Very bad costing estimation on gin vs gist with FTS |