Re: pgsql: Define a separately configurable XLOG_BLCKSZ symbol for the page

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Define a separately configurable XLOG_BLCKSZ symbol for the page
Date: 2006-04-04 13:36:09
Message-ID: 18386.1144157769@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> This is a patch for write performance, but here theoretically decreases the
> read performance due to the possible setting of XLOG_BLCKSZ (say 512 as
> sector size, which is << BLCKSZ). It maybe avoidable by still using BLCKSZ
> or even more aggresive block size, but may also need some local tweak here.

(1) I really don't think we care that much about read performance on xlog.

(2) Buffering should be the kernel's problem, not ours. Since we don't
specify O_DIRECT during reading, the kernel ought to be perfectly
capable of recognizing the opportunity for read-ahead on these fetches.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User H-saito 2006-04-04 18:02:40 psqlodbc - psqlodbc: upgrade version 07.03.0262 of *nix.
Previous Message Qingqing Zhou 2006-04-04 09:23:05 Re: pgsql: Define a separately configurable XLOG_BLCKSZ symbol for the page