Re: Sequences change in a rolled-back transactions - Mailing list pgsql-general

From Craig Ringer
Subject Re: Sequences change in a rolled-back transactions
Date
Msg-id 49B53977.2070706@postnewspapers.com.au
Whole thread Raw
In response to Re: Sequences change in a rolled-back transactions  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
Alvaro Herrera wrote:
> Erwin Moller wrote:
>
>> I thought a transaction that is rolled back, rolls back *everything*
>> done in that transaction.
>> Appearantly sequences are not included.
>
> Yes.  This is actually a desirable property, because it allows sequences
> to work fine in concurrent scenarios (which are, after all, the whole
> point of sequences).
>
> If you actually need an incremental number with no gaps (which is rare
> but not unseen), you need to use some other mechanism, which will
> probably involve a lock to prevent concurrency.

If so, search the list archives for "gapless sequence". You'll see lots
of explanations of options and of the problems with them.

--
Craig Ringer

pgsql-general by date:

Previous
From: Justin Funk
Date:
Subject: Get IP addresses from tsvectors
Next
From: George Oakman
Date:
Subject: C++ User-defined functions