| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: configure option for XLOG_BLCKSZ |
| Date: | 2008-05-03 17:14:35 |
| Message-ID: | 9728.1209834875@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> 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...
I think the use-case for varying the WAL segment size is unrelated to
performance of the master server, but would instead be concerned with
adjusting the granularity of WAL log shipping.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-03 17:17:34 | Re: [COMMITTERS] pgsql: Sigh ... |
| Previous Message | Tom Lane | 2008-05-03 17:12:41 | Re: Exposing keywords to clients |