Re: copy.c allocation constant - Mailing list pgsql-hackers

From Robert Haas
Subject Re: copy.c allocation constant
Date
Msg-id CA+TgmobV1U8twJbecfbCxLxggWK3vuJQ_8tutogYDALOOjHMFA@mail.gmail.com
Whole thread Raw
In response to Re: copy.c allocation constant  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: copy.c allocation constant
Re: copy.c allocation constant
List pgsql-hackers
On Wed, Jan 24, 2018 at 12:25 PM, Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> At the glibc level ... I'm not so sure. AFAIK glibc uses an allocator
> with similar ideas (freelists, ...) so hopefully it's fine too.
>
> And then there are the systems without glibc, or with other libc
> implementations. No idea about those.

My guess is that a fairly common pattern for larger chunks will be to
round the size up to a multiple of 4kB, the usual memory page size.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Add parallel-aware hash joins.
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Add parallel-aware hash joins.