Subject: Re: Column with recycled sequence value
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Michael Fuhr <mike@fuhr.org>
Cc: =?ISO-8859-1?Q?K=D6PFERL?= Robert <robert.koepferl@sonorys.at>,
	"'pgsql-sql@postgresql.org'" <pgsql-sql@postgresql.org>
In-Reply-To: <20050113211903.GA41687@winnie.fuhr.org>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB1654B@neptun.sonorys.at>
	<1105649326.24795.99.camel@state.g2switchworks.com>
	<20050113211903.GA41687@winnie.fuhr.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1105651913.24795.102.camel@state.g2switchworks.com>
Mime-Version: 1.0
Date: Thu, 13 Jan 2005 15:31:54 -0600

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=C3=96PFERL Robert wrote:
>=20
> > > suppose I have a let's say heavy used table. There's a column contain=
ing
> > > UNIQUE in4
> > > values. The data type musn't exceed 32-Bit. Since however the table i=
s heavy
> > > used 2^32 will be reached soon and then? There are far less than 4G-r=
ecords
> > > saved thus these values may be reused. How can this be accomplished?
> > >=20
> > > I already defined a sequence but then?
> >=20
> > Redefine it as a bigserial?
>=20
> 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.