Re: configure option for XLOG_BLCKSZ - Mailing list pgsql-patches

From Simon Riggs
Subject Re: configure option for XLOG_BLCKSZ
Date
Msg-id 1210009943.4435.108.camel@ebony.site
Whole thread Raw
In response to Re: configure option for XLOG_BLCKSZ  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Mon, 2008-05-05 at 13:06 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> >> On Sat, 03 May 2008 13:14:35 -0400 Tom Lane wrote:
> >>> 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.
>
> > Seems the stuff to zero out the unused segment tail would be more useful
> > here.
>
> Well, that's also useful, but it hardly seems like a substitute for
> picking a more optimal segment size in the first place.

I can't imagine having separately compiled executables depending upon
the write rate of different applications. What would you do if the write
rate increases over time (like it usually does)? How would you manage a
server farm like that? There's no practical answer there, just a great
way to introduce instability where there previously wasn't any.

--
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: configure option for XLOG_BLCKSZ
Next
From: Magnus Hagander
Date:
Subject: Re: win32mak_patch