Re: Sequence Access Method WIP
Petr Jelinek <petr@2ndquadrant.com>
From: Petr Jelinek <petr@2ndquadrant.com>
To: Craig Ringer <craig@2ndquadrant.com>,
Heikki Linnakangas <hlinnakangas@vmware.com>,
Andres Freund <andres@2ndquadrant.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2014-11-07T16:35:13Z
Lists: pgsql-hackers
On 06/11/14 11:22, Craig Ringer wrote: > On 11/05/2014 05:01 AM, Petr Jelinek wrote: >> I guess I could port BDR sequences to this if it would help (once we >> have bit more solid agreement that the proposed API at least >> theoretically seems ok so that I don't have to rewrite it 10 times if at >> all possible). > > Because the BDR sequences rely on all the other BDR machinery I suspect > that'd be a pretty big thing to review and follow for someone who > doesn't know the BDR code. > > Do you think it'd be simple to provide a blocking, transactional > sequence allocator via this API? i.e. gapless sequences, much the same > as typically implemented with SELECT ... FOR UPDATE on a counter table. > > It might be more digestible standalone, and would be a handy contrib/ > example extension demonstrating use of the API. > Yes I think that's doable (once we iron out the API we can agree on). -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Add missing gss option to msvc config template
- 3063e7a84026 9.6.0 cited