Does setval(nextval()+N) generate unique blocks of IDs?

From: Craig James <cjames(at)emolecules(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Does setval(nextval()+N) generate unique blocks of IDs?
Date: 2012-08-20 23:32:27
Message-ID: CAFwQ8re6hFodxhfRcsrpywegFfRAVd9a3fe=9BOXL2dtezMEAQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Is seq.setval() "non transactional" in the same sense as seq.nextval()
is? More specifically, suppose I sometimes want to get IDs one-by-one
using nextval(), but sometimes I want a block of a thousand IDs. To
get the latter, I want to do this:

select setval('object_id_seq', nextval('object_id_seq') + 1000, false);

Now suppose two processes do this simultaneously. Maybe they're in
transactions, maybe they're not. Are they guaranteed to get distinct
blocks of IDs? Or is it possible that each will execute nextval() and
get N and N+1 respectively, and then do setval() to N+1000 and N+1001,
resulting in two overlapping blocks.

If the answer is, "This won't work," then what's a better way to do this?

Thanks,
Craig

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2012-08-21 00:10:00 Re: Does setval(nextval()+N) generate unique blocks of IDs?
Previous Message delongboy 2012-08-20 20:51:09 Re: Increasing WAL usage followed by sudden drop