| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, 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 12:33:08 |
| Message-ID: | 20131010123308.GK2706@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> I think it would be even simpler, and more reliable, to start with the
> parameter to initdb - I like that. But instead of having it set a new
> variable based on that and then autotune off that, just have *initdb*
> do these calculations you're suggesting, and write new defaults to the
> files (preferably with a comment).
Agreed; I especially like having the comment included.
> That way if the user *later* comes in and say changes shared_buffers,
> we don't dynamically resize the work_mem into a value that might cause
> his machine to die from swapping which would definitely violate the
> principle of least surprise..
+1
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-10 12:59:47 | Re: space reserved for WAL record does not match what was written: panic on windows |
| Previous Message | Stephen Frost | 2013-10-10 12:31:20 | Re: Auto-tuning work_mem and maintenance_work_mem |