Re: Auto-tuning work_mem and maintenance_work_mem
От | Magnus Hagander |
---|---|
Тема | Re: Auto-tuning work_mem and maintenance_work_mem |
Дата | |
Msg-id | CABUevExuipZH9KzK8dtPpX74QBrxhgGzaz_SkZFQ5wPxDo9uhw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Auto-tuning work_mem and maintenance_work_mem (Christopher Browne <cbbrowne@gmail.com>) |
Список | pgsql-hackers |
On Thu, Oct 10, 2013 at 9:41 PM, Christopher Browne <cbbrowne@gmail.com> wrote: > On Thu, Oct 10, 2013 at 12:28 PM, Bruce Momjian <bruce@momjian.us> wrote: >> How do we handle the Python dependency, or is this all to be done in >> some other language? I certainly am not ready to take on that job. > > I should think it possible to reimplement it in C. It was considerably > useful to start by implementing in Python, as that evades various sorts > of efforts needed in C (e.g. - memory allocation, picking a hash table > implementation), and allows someone to hack on it without needing to > run through a recompile every time something is touched. I think in the context of this problem, reimplementing that from python to C is the easiest part. Actually figuring out what the tool should *do* and how it should do it is the hard part. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: