Re: Auto incrementing primary keys - Mailing list pgsql-general

From Reid Thompson
Subject Re: Auto incrementing primary keys
Date
Msg-id 1203379767.27833.5.camel@endpoint
Whole thread Raw
In response to Re: Auto incrementing primary keys  (Raymond O'Donnell <rod@iol.ie>)
List pgsql-general
On Mon, 2008-02-18 at 17:46 +0000, Raymond O'Donnell wrote:
> On 18/02/2008 13:14, pgsql_user wrote:
> > so wouldnt I run out of ids one day, if there are lot of failed insert
> > statements, lets say for every successful insert there are 50
> > unsuccessful inserts, so ids would be 1, 50, 100, and once I have
> > thousands of rows, I will run out of IDs ? should I use bigserial
> > instead ?
>
> Well, that depends on your usage, so only you can answer that. According
> to the docs, "serial" creates an integer column,  which will give you
> 2147483647 values - how quickly will you use that lot up? If you think
> you will run out, by all means use bigserial.
>
> Ray.
>
> ---------------------------------------------------------------
> Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
> rod@iol.ie
> ---------------------------------------------------------------
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

http://www.google.com/search?q=2147483647+seconds+to
+years&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:official&client=firefox-a

at one per second.
2 147 483 647 seconds = 68.0511039 years


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Pains in upgrading to 8.3
Next
From: "Markus Bertheau"
Date:
Subject: out-of-line (TOAST) storage ineffective when loading from dump?