Re: configure option for XLOG_BLCKSZ

From: "Mark Wong" <markwkm(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: configure option for XLOG_BLCKSZ
Date: 2008-05-02 18:34:18
Message-ID: 70c01d1d0805021134x11d2a98o57875ee7d73792d6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Fri, May 2, 2008 at 9:16 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Mark Wong" <markwkm(at)gmail(dot)com> writes:
>
> > I still believe it makes sense to have them separated. I did have
> > some data, which has since been destroyed, that suggested there were
> > some system characterization differences for OLTP workloads with
> > PostgreSQL. Let's hope those disks get delivered to Portland soon. :)
>
> Fair enough. It's not that much more code to have another configure
> switch --- will go do that.
>
> If we are allowing blocksize and relation seg size to have configure
> switches, seems that symmetry would demand that XLOG_SEG_SIZE be
> configurable as well. Thoughts?

I don't have a feel for this one, but when we get the disks set up we
can certainly test to see what effects it has. :)

Regards,
Mark

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2008-05-02 19:27:05 Re: [COMMITTERS] pgsql: Sigh ...
Previous Message Simon Riggs 2008-05-02 17:52:10 Re: [HACKERS] GUC parameter cursors_tuple_fraction