Re: Auto-tuning work_mem and maintenance_work_mem

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(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 03:35:17
Message-ID: CAM3SWZROaBFRpeaDmob+azsiQMCTH_srqtzf8Op7TSOjYGnypQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 9, 2013 at 8:20 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I am not sure that having that external to the backend really makes
> sense because I am concerned people will not use it. We can certainly
> add it to change our defaults, of course. Also consider many installs
> are automated.

Sure.

I was imagining that we'd want to write the tool with the idea in mind
that it was usually run immediately after initdb. We'd reach out to
packagers to have them push it into the hands of users where that's
practical.

If you think that sounds odd, consider that on at least one popular
Linux distro, installing MySQL will show a ncurses interface where the
mysql password is set. We wouldn't need anything as fancy as that.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-10-10 03:47:04 Re: Patch: FORCE_NULL option for copy COPY in CSV mode
Previous Message Bruce Momjian 2013-10-10 03:20:35 Re: Auto-tuning work_mem and maintenance_work_mem