Re: pgsql: Generational memory allocator - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Generational memory allocator
Date
Msg-id CANP8+j+LZNRt79coE_oV5L3kAtGCULkTGz59_DLvnt1F7tceaQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Generational memory allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 27 November 2017 at 09:06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> On 27 November 2017 at 06:42, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Sold, will make it so.
>
>> So you will like this next patch also, since there is related code
>> above that stanza.
>
> Looks reasonable to me, but I wonder whether BLCKSZ is a good initial
> setting.  Since the data length is only uint16, we're apparently assuming
> that the contents must be small.

Our max block size is 2^15 so I think we're good.

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


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Generational memory allocator
Next
From: Magnus Hagander
Date:
Subject: pgsql: Fix typo in comment