| From: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: configure option for XLOG_BLCKSZ |
| Date: | 2008-05-03 17:26:12 |
| Message-ID: | 20080503192612.04c14767@iridium.wars-nicht.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sat, 03 May 2008 13:14:35 -0400 Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
>
> > 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.
*nod* I heard this argument several times. Simon: there was a discussion
about this topic in Prato last year. Since WAL logfiles are usually
binary stuff, the files can't be compressed much so a smaller logfile
size on a not-so-much-used system would save a noticeable amount of
bandwith (and cpu cycles for compression).
Kind regards
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-03 17:34:05 | Re: create or replace language |
| Previous Message | Tom Lane | 2008-05-03 17:17:34 | Re: [COMMITTERS] pgsql: Sigh ... |