| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2011-02-20 14:48:06 | Re: using a lot of maintenance_work_mem |
| Previous Message | Bruce Momjian | 2011-02-20 14:32:02 | Re: using a lot of maintenance_work_mem |