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

From Simon Riggs
Subject Re: pgsql: Generational memory allocator
Date
Msg-id CANP8+jJTVM+mVTwgKXh5T-v3oV3RsXZ5Nu-5S+UF5b+pqSARpA@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Generational memory allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Generational memory allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 27 November 2017 at 06:42, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> On 27 November 2017 at 05:53, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Well, let's not overthink this, because anything under 8K is going to
>>> be rounded up to the next power of 2 anyway by aset.c.  Based on this
>>> point I'd say that BLCKSZ/2 or BLCKSZ/4 would be reasonable candidates
>>> for the minimum.
>
>> BLCKSZ/2 seems best then.
>
> Sold, will make it so.

So you will like this next patch also, since there is related code
above that stanza.

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

Attachment

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Pad XLogReaderState's main_data buffer more aggressively.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Generational memory allocator