Skip site navigation (1) Skip section navigation (2)

Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize
Date: 2013-06-22 10:39:15
Message-ID: CA+U5nMKkRMin1pV8VMpS6_n7hcOWSG0kZS3oFL9JOa8DV6vJyQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 22 June 2013 08:46, Stephen Frost <sfrost(at)snowman(dot)net> wrote:

>>The next limit faced by sorts is
>> INT_MAX concurrent tuples in memory, which limits helpful work_mem to about
>> 150 GiB when sorting int4.
>
> That's frustratingly small. :(
>

But that has nothing to do with this patch, right? And is easily fixed, yes?

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


In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2013-06-22 11:32:46
Subject: Re: XLogInsert scaling, revisited
Previous:From: Simon RiggsDate: 2013-06-22 10:36:45
Subject: Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group