Re: checkpointer continuous flushing - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: checkpointer continuous flushing
Date
Msg-id CAB7nPqS4GY3C_T-WyM_52D-ux4_BM0rdUJh+0wuZg0dYaBCfpA@mail.gmail.com
Whole thread Raw
In response to Re: checkpointer continuous flushing  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Aug 11, 2015 at 4:28 AM, Andres Freund wrote:
> On August 10, 2015 8:24:21 PM GMT+02:00, Fabien COELHO wrote:
>>> You can't allocate 4GB with palloc(), it has a builtin limit against
>>> allocating more than 1GB.
>>
>>Argh, too bad, I assumed very naively that palloc was malloc in
>>disguise.
>
> It is, but there's some layering (memory pools/contexts) on top. You can get huge allocations with polloc_huge.

palloc_huge does not exist yet ;)
There is either repalloc_huge or palloc_extended now, though
implementing one would be trivial.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.
Next
From: Joe Conway
Date:
Subject: Re: [patch] A \pivot command for psql