X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6750732A75E for ; Wed, 20 Oct 2004 16:20:45 +0100 (BST) 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 58274-02 for ; Wed, 20 Oct 2004 15:20:37 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 911C232A10D for ; Wed, 20 Oct 2004 16:20:35 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9KFKWJ7060083 for ; Wed, 20 Oct 2004 15:20:32 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9KFGjsT032511 for pgsql-general@postgresql.org; Wed, 20 Oct 2004 15:16:45 GMT From: David Ecker Subject: Re: Sequence question X-Newsgroups: comp.databases.postgresql.general References: Lines: 46 User-Agent: KNode/0.7.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Message-ID: <1098285405.OfvaWaCsriLMf7T5iDLfwA@ultrafeed> X-Abuse-Report: http://www.usenetabuse.com X-Orginal-Message-ID: Date: Wed, 20 Oct 2004 17:16:44 +0200 To: pgsql-general@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/905 X-Sequence-Number: 67428 Far from being a perfect idea but a faster solution than stepping through all holes: 1) Create a second table containing only one field of type of your key. 2) When you delete an entry place the delete key value in your second table 3) If you insert a new entry into your old table and your new table contains a value, take the minimum value in the new table as your new key and delete that entry from the new table. If the new table is empty just use the sequence to get the new key value. Hope that helps David Ecker Eric E wrote: > Hi, > I have a question about sequences. I need a field to have values > with no holes in the sequence. However, the values do not need to be in > order. > > My users will draw a number or numbers from the sequence and write to > the field. Sometimes, however, these sequence numbers will be discarded > (after a transaction is complete), and thus available for use. During > the transaction, however, any drawn numbers need to be unavailable. > I would like the next user who draws a number to draw the lowest number > she can, starting with the holes in the sequence. > > This continuous sequence is absolutely required by our company, as the > fact that the sequence has no holes is used to check for much more > serious problems. > > So my question is: > what's the most effective way to get the next available number? > > My present method is to do a query that finds the first and last number > in each of the holes, step through those holes, and then start > generating new numbers. Unfortunately, this involves doing a table scan > each time - before I generate the number, and does not produce the > transaction-safety I want. > > Does anyone have any better ideas? Places I should look? > > Thanks, > > Eric