| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| 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> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-10 17:37:22 |
| Message-ID: | 5256E5D2.2080901@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
All,
We can't reasonably require user input at initdb time, because most
users don't run initdb by hand -- their installer does it for them. So
any "tuning" which initdb does needs to be fully automated.
So, the question is: can we reasonably determine, at initdb time, how
much RAM the system has?
I also think this is where the much-debated ALTER SYSTEM SET suddenly
becomes valuable. With it, it's reasonable to run a "tune-up" tool on
the client side. I do think it's reasonable to tell a user:
"Just installed PostgreSQL? Run this command to tune your system:"
Mind you, the tuneup tool I'm working on makes use of Python,
configuration directory, and Jinga2, so it's not even relevant to the
preceeding.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-10-10 17:49:34 | Re: pg_stat_statements: calls under-estimation propagation |
| Previous Message | Fujii Masao | 2013-10-10 17:36:09 | Re: Compression of full-page-writes |