Re: pg_sequence catalog - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_sequence catalog
Date
Msg-id 20160831154153.nabgqkywwh7accw6@alap3.anarazel.de
Whole thread Raw
In response to Re: pg_sequence catalog  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_sequence catalog  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 2016-08-31 11:23:27 -0400, Tom Lane wrote:
> Another issue is what is the low-level interlock between nextvals
> in different processes.  Right now it's the buffer lock on the
> sequence's page.  With a scheme like this, if we just kept doing
> that, we'd have a single lock covering probably O(100) different
> sequences which might lead to contention problems.  We could probably
> improve on that with some thought.

I was thinking of forcing the rows to be spread to exactly one page per
sequence...

Andres



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: proposal: psql \setfileref
Next
From: Andres Freund
Date:
Subject: Re: Optimizing aggregates