| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Wong <markwkm(at)gmail(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: configure option for XLOG_BLCKSZ |
| Date: | 2008-05-03 11:42:08 |
| Message-ID: | 1209814928.4264.265.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Fri, 2008-05-02 at 12:28 -0400, Greg Smith wrote:
> As PostgreSQL makes its way into higher throughput environments, it
> wouldn't surprise me to discover more of these situations where switching
> WAL segments every 16MB turns into a bottleneck.
We already hit that issue and fixed it early in the 8.3 cycle. It was
more of a problem than the checkpoint issue because it caused hard
lock-outs while the file switches occurred. It didn't show up unless you
looked at the very detailed transaction result data because on fast
systems we are file switching every few seconds.
Not seen any gains from varying the WAL file size since then...
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-05-03 13:11:26 | Re: [COMMITTERS] pgsql: Sigh ... |
| Previous Message | Peter Eisentraut | 2008-05-03 09:17:38 | Re: Exposing keywords to clients |