| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-11 17:32:45 |
| Message-ID: | CABUevExuipZH9KzK8dtPpX74QBrxhgGzaz_SkZFQ5wPxDo9uhw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 10, 2013 at 9:41 PM, Christopher Browne <cbbrowne(at)gmail(dot)com> wrote:
> On Thu, Oct 10, 2013 at 12:28 PM, Bruce Momjian <bruce(at)momjian(dot)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 Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-10-11 17:57:56 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Previous Message | Andres Freund | 2013-10-11 17:06:55 | Re: Compression of full-page-writes |