Re: pgsql: Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, bu

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, bu
Date: 2011-01-26 03:02:18
Message-ID: 201101260302.p0Q32I125279@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> If you aren't willing to deal with a variable value for the block size,
> >> please revert this patch.
>
> > The problem is that I have hard-coded 8k into various text strings and I
> > didn't want to make that variable. How should it behave if they are
> > using a non-8k wal buffer size? Should it still use 8k or not? I
> > figured throwing an error would at least alert them to the mismatch.
>
> Well, as I said, if you aren't willing to put effort into that point,
> just revert the patch. Making the program refuse to do anything doesn't
> help *anyone*. Stats taken using a fixed 8K blocksize are better than
> no stats at all.

Sure I am willing to fix it. Should I have it always use the value of
XLOG_BLCKSZ for its tests, and adjust the output text accordingly?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-01-26 03:06:26 Re: pgsql: Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, bu
Previous Message Tom Lane 2011-01-26 03:00:37 Re: pgsql: Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, bu