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

Re: work_mem / maintenance_work_mem maximums

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: work_mem / maintenance_work_mem maximums
Date: 2011-02-20 14:41:49
Message-ID: 201102201441.p1KEfn725347@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Josh Berkus wrote:
> 
> > Is this a TODO?  Can we easily fix the tuplesort.c code?
> 
> Easily, no.  But that's not a reason for it to not be a TODO.
> 
> I, too, would like to be able to make use of 32GB of work_mem effectively.

[ repost to the right thread.]

Well, I figure it will be hard to allow larger maximums, but can we make
the GUC variable maximums be more realistic?  Right now it is
MAX_KILOBYTES (INT_MAX).

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

pgsql-hackers by date

Next:From: Bernd HelmleDate: 2011-02-20 14:48:06
Subject: Re: using a lot of maintenance_work_mem
Previous:From: Bruce MomjianDate: 2011-02-20 14:32:02
Subject: Re: using a lot of maintenance_work_mem

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