| From: | Peter Eisentraut <peter_e(at)gmx(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 18:53:21 |
| Message-ID: | 5256F7A1.6080305@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/10/13 11:45 AM, Bruce Momjian wrote:
> I think the big win for a tool would be to query the user about how they
> are going to be using Postgres, and that can then spit out values the
> user can add to postgresql.conf, or to a config file that is included at
> the end of postgresql.conf.
I think such a tool would actually make the initial experience worse for
many people. Quick, how are you going to use your PostgreSQL server:
- OLTP
- web
- mixed
Uh, all of the above? This sort of thing can quickly turn the "first 15
minutes" into the first 2 hours, as users are forced to analyze the
different settings, have second thoughts, wonder about how to change
them back, etc. The fewer decisions people have to make initially, the
better. The initdb phase already has too many required decisions that
can cause regret later (e.g., locale, encoding, checksums).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Munro | 2013-10-10 18:56:49 | Re: [v9.4] row level security |
| Previous Message | Fujii Masao | 2013-10-10 18:52:42 | Re: strange behavior of pg_trgm's similarity function |