| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: checkpointer continuous flushing |
| Date: | 2015-08-11 00:37:56 |
| Message-ID: | CAB7nPqS4GY3C_T-WyM_52D-ux4_BM0rdUJh+0wuZg0dYaBCfpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2015-08-11 00:44:02 | Re: [patch] A \pivot command for psql |
| Previous Message | Tom Lane | 2015-08-10 23:29:04 | Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types. |