| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: auto-sizing wal_buffers |
| Date: | 2011-01-13 23:02:12 |
| Message-ID: | 4D2F8474.7020608@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Depends what people want to do. We could make the default "0kB", and
> define that to mean "auto-tune", or we could remove the parameter
> altogether. I think I was envisioning the latter, but if people are
> hesitant to do that we could do the former instead.
Unfortunately, we might still need a manual parameter for override
because of the interaction between wal_buffers and
synchronous_commit=off, since it sets the max size of the unflushed data
buffer. Discuss?
And the "auto" setting should be -1, not 0kB. We use -1 for "use
default" for several other GUCs.
Other than that, I think Greg's numbers are fine, and strongly support
having one less thing to tune.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-13 23:06:24 | Re: auto-sizing wal_buffers |
| Previous Message | Noah Misch | 2011-01-13 23:01:24 | ALTER TYPE 7: avoid index rebuilds/FK validations |