Tom Lane wrote:
Now, what should we call it instead?  I haven't come up with any
compelling thoughts --- the best I can do is "big_sort_mem" or
"single_sort_mem".  Surely someone out there has a better idea.

BTW, does anyone want to lobby for renaming sort_mem at the same time?
Since it's used for sizing hash tables as well as sort workspace, it's
rather misnamed.  I hesitate to rename it because of the potential for
confusion though.  People are pretty used to the existing name.

Hmmm ... maybe query_work_mem and maintenance_work_mem, or something similar?


Joe



---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to