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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
