| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Smith <gsmith(at)gregsmith(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Decibel! <decibel(at)decibel(dot)org> |
| Subject: | Re: Overhauling GUCS |
| Date: | 2008-06-11 16:37:22 |
| Message-ID: | 484FFF42.7000408@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Oh, and wal_buffers, the default for which we should just change if it
>> weren't for SHMMAX.
>
> Uh, why? On a workload of mostly small transactions, what value is
> there in lots of wal_buffers?
Actually, it's also useful for any workload with many connections. Any
time you have high throughput, really. We've seen this on DBT2,
SpecJAppserver and iGen.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-06-11 16:38:47 | Re: Overhauling GUCS |
| Previous Message | Josh Berkus | 2008-06-11 16:36:22 | Re: Overhauling GUCS |