X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 01F273A5D37 for ; Thu, 13 Jan 2005 21:26:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20861-09 for ; Thu, 13 Jan 2005 21:26:19 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 606BC3A5C2B for ; Thu, 13 Jan 2005 21:19:09 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j0DLJ3Rd053362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2005 14:19:06 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j0DLJ3Vs041754; Thu, 13 Jan 2005 14:19:03 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j0DLJ3ap041753; Thu, 13 Jan 2005 14:19:03 -0700 (MST) (envelope-from mfuhr) Date: Thu, 13 Jan 2005 14:19:03 -0700 From: Michael Fuhr To: Scott Marlowe Cc: =?iso-8859-1?Q?K=D6PFERL?= Robert , "'pgsql-sql@postgresql.org'" Subject: Re: Column with recycled sequence value Message-ID: <20050113211903.GA41687@winnie.fuhr.org> References: <1105649326.24795.99.camel@state.g2switchworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1105649326.24795.99.camel@state.g2switchworks.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/88 X-Sequence-Number: 19876 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? -- Michael Fuhr http://www.fuhr.org/~mfuhr/