Re: [HACKERS] work_mem / maintenance_work_mem maximums

2011-02-20 Thread Bruce Momjian
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

Re: [HACKERS] work_mem / maintenance_work_mem maximums

2011-02-19 Thread Bruce Momjian
Stephen Frost wrote: -- Start of PGP signed section. Greetings, After watching a database import go abysmally slow on a pretty beefy box with tons of RAM, I got annoyed and went to hunt down why in the world PG wasn't using but a bit of memory. Turns out to be a well known and

Re: [HACKERS] work_mem / maintenance_work_mem maximums

2011-02-19 Thread Josh Berkus
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. -- -- Josh Berkus