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
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2013-06-22 11:32:46|
|Subject: Re: XLogInsert scaling, revisited|
|Previous:||From: Simon Riggs||Date: 2013-06-22 10:36:45|
|Subject: Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize|