| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | DFE <mimmopasticcio(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: type "serial" and biginteger |
| Date: | 2011-09-27 15:57:01 |
| Message-ID: | CAHyXU0xdigiVewFri9HaMk12xBZby+p+hA8iXt6NnfKf+E6OJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Tue, Sep 27, 2011 at 5:16 AM, DFE <mimmopasticcio(at)gmail(dot)com> wrote:
> Hi all,
> I create a table with Primary Key with name "gid" and type SERIAL.
> I have a dubt on the SERIAL type: this data type is a INTEGER (int4)
> type, but the sequence that is automatically created with pgAdmin has
> BIGINTEGER output (MAXVALUE 9223372036854775807).
> This fact can cause a numeric overflow during the insert?
yup -- if you're really worried about this, use BIGSERIAL. you could
in theory cap the sequence, but you'd just be trading one error for
another.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nomeneta Saili | 2011-09-28 03:23:12 | PostgreSQL ANSI OBDC Installation |
| Previous Message | Tom Lane | 2011-09-27 13:58:19 | Re: plperl.so no such file or directory |