On Thu, May 15, 2014 at 9:06 PM, Bruce Momjian <br...@momjian.us> wrote: > > This is the same problem we had with auto-tuning work_mem, in that we > didn't know what other concurrent activity was happening. Seems we need > concurrent activity detection before auto-tuning work_mem and > effective_cache_size. >
Perhaps I am missing something obvious here, but would mmgr have any useful numbers on this? Like any book-keeping info maintained by mcxt.c/aset.c? Would extending that interface help? -- Amit -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
