| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-17 15:55:14 |
| Message-ID: | 1382025314.97411.YahooMailNeo@web162906.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I still think my previous proposal of increasing the defaults for
> work_mem and maintenance_work_mem by 4X would serve many more
> people well than it would serve poorly. I haven't heard anyone
> disagree with that notion. Does anyone disagree? Should we do
> it?
I think that it makes sense to do that. Those are still reasonable
defaults for a machine with 2GB of RAM, maybe even with less.
We're talking about putting this only in a release that will come
out in 2014. How many machines used for a database server that new
will have less than that?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-10-17 16:03:01 | Re: Auto-tuning work_mem and maintenance_work_mem |
| Previous Message | Alvaro Herrera | 2013-10-17 15:42:46 | Re: [COMMITTERS] pgsql: Rework SSL renegotiation code |