Re: Sequence Access Method WIP - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Sequence Access Method WIP
Date
Msg-id CA+U5nM+cXmO6cEpkZMcsQhgY99SfGCDGBWp7oOQpcjpcrL_BdQ@mail.gmail.com
Whole thread Raw
In response to Re: Sequence Access Method WIP  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Sequence Access Method WIP  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On 18 November 2013 07:36, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
> On 14.11.2013 22:10, Simon Riggs wrote:
>>
>> Includes test extension which allows sequences without gaps - "gapless".
>
>
> I realize this is just for demonstration purposes, but it's worth noting
> that it doesn't actually guarantee that when you use the sequence to
> populate a column in the table, the column would not have gaps. Sequences
> are not transactional, so rollbacks will still produce gaps. The
> documentation is misleading on that point. Without a strong guarantee, it's
> a pretty useless extension.

True.

If I fix that problem, I should change the name to "lockup" sequences,
since only one transaction at a time could use the nextval.

Should I change the documentation, or just bin the idea?

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alexey Vasiliev
Date:
Subject: Re[2]: [HACKERS] Connect from background worker thread to database
Next
From: Simon Riggs
Date:
Subject: Re: Sequence Access Method WIP