On Mon, Oct 17, 2011 at 2:43 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > There really is not any way to generate guaranteed-hole-free sequences > using sequence objects. If you have to have that, I'd suggest locking > the table against other writes and then fetching MAX(id) + 1. It's not > very fast, and it's not at all concurrent, but that's the price of > ensuring no holes. Personally I'd rethink how badly you need that > property. >
another option is to create a table to use as a sequence, and lock that table everytime you need a new value... is not concurrent also, but at least faster... unless i'm missing something -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
