Re: Auto-tuning work_mem and maintenance_work_mem

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: 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-10 16:39:04
Message-ID: 5256D828.3030502@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/10/2013 12:28 PM, Bruce Momjian 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.

Without considering any wider question here, let me just note this:

Anything that can be done in this area in Python should be doable in
Perl fairly simply. I don't think we should be adding any Python
dependencies. For good or ill Perl has been used for pretty much all our
complex scripting (pgindent, MSVC build system etc.)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-10-10 16:45:31 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Kevin Grittner 2013-10-10 16:37:58 Re: [COMMITTERS] pgsql: Add record_image_ops opclass for matview concurrent refresh.