Re: Column with recycled sequence value - Mailing list pgsql-sql

From Scott Marlowe
Subject Re: Column with recycled sequence value
Date
Msg-id 1105651913.24795.102.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: Column with recycled sequence value  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Column with recycled sequence value  (Andrew Sullivan <ajs@crankycanuck.ca>)
Re: Column with recycled sequence value  (Michael Fuhr <mike@fuhr.org>)
List pgsql-sql
On Thu, 2005-01-13 at 15:19, Michael Fuhr wrote:
> On Thu, Jan 13, 2005 at 02:48:47PM -0600, Scott Marlowe wrote:
> > On Thu, 2005-01-13 at 11:08, KÖPFERL Robert wrote:
>
> > > suppose I have a let's say heavy used table. There's a column containing
> > > UNIQUE in4
> > > values. The data type musn't exceed 32-Bit. Since however the table is heavy
> > > used 2^32 will be reached soon and then? There are far less than 4G-records
> > > saved thus these values may be reused. How can this be accomplished?
> > >
> > > I already defined a sequence but then?
> >
> > Redefine it as a bigserial?
>
> That would violate the 32-bit requirement since bigserial would
> make the field a bigint (64 bits).  Or am I missing something?

I wasn't sure if that was a limitation he was facing due to business
rules or if he was referring to the limit in postgresql.

Any method that tries to reuse sequence numbers is a bad idea (TM) and
to be avoided, so my point in asking was if the user didn't know about
bigserial / bigint.


pgsql-sql by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Column with recycled sequence value
Next
From: Andrew Sullivan
Date:
Subject: Re: Column with recycled sequence value