Re: pg_sequence catalog - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_sequence catalog
Date
Msg-id 7079.1472666388@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_sequence catalog  (andres@anarazel.de (Andres Freund))
Responses Re: pg_sequence catalog  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
andres@anarazel.de (Andres Freund) writes:
> On 2016-08-31 14:25:43 -0300, Alvaro Herrera wrote:
>> Yes, sure, we're still improving even if we stick to one-seq-per-bufpage,
>> but while we're at it, we could as well find a way to make it as best as
>> we can.  And allowing multiple seqs per page seems a much better
>> situation, so let's try to get there.

> It's not really that simple. Having independent sequence rows closer
> together will have its own performance cost.

You are ignoring the performance costs associated with eating 100x more
shared buffer space than necessary.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Use static inline functions for float <-> Datum conversions.
Next
From: Andres Freund
Date:
Subject: Re: pg_sequence catalog