| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | MauMau <maumau307(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Auto-tuning work_mem and maintenance_work_mem |
| Date: | 2013-10-15 17:19:06 |
| Message-ID: | 525D790A.9030002@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/15/2013 05:52 AM, Magnus Hagander wrote:
> But the argument about being friendly for new users should definitely
> have us change wal_level and max_wal_senders.
+1 for having replication supported out-of-the-box aside from pg_hba.conf.
To put it another way: users are more likely to care about replication
than they are about IO overhead on a non-replicated server. And for the
users who care about IO overhead, they are more likely to much about in
pg.conf *anyway* in order to set a slew of performance-tuning settings.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-10-15 17:19:17 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Previous Message | Robert Haas | 2013-10-15 16:56:17 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |