| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | andres(at)anarazel(dot)de (Andres Freund) |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_sequence catalog |
| Date: | 2016-08-31 17:59:48 |
| Message-ID: | 7079.1472666388@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-08-31 18:01:46 | Re: pg_sequence catalog |
| Previous Message | Tom Lane | 2016-08-31 17:48:18 | Re: [COMMITTERS] pgsql: Use static inline functions for float <-> Datum conversions. |