On Sun, Jul 6, 2008 at 6:15 PM, Jack Brown <[EMAIL PROTECTED]> wrote: > Dear list, > > I need some tips and/or pointers to relevant documentation implementing (what > I chose to call) "a perfect sequence" i.e. a sequence that has no missing > numbers in the sequence. I'd like it to auto increment on insert, and auto > decrement everything bigger than its value on delete. There are many > mechanisms (rules, triggers, sequences, locks etc.) but I'm not sure which > combination would result in the most elegant implementation.
This would actually be a perfectly awful sequence. :) Seriously, it's costly to lock the whole table, set the sequence to the last available value and lock it in terms of concurrency. > > Oh, and if you know the right term for what I just described, I'd be more > than pleased to hear it! :-) I believe it's called a "How to destroy concurrency" or something like that. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
