On Thu, Feb 18, 2010 at 7:04 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Magnus Hagander wrote:
>> O_DIRECT helps us when we're not going to read the file again, because
>> we don't waste cache on it. If we are, which is the case here, it
>> should be really bad for performance, since we actually have to do a
>> physical read.
>>
>> Incidentally, that should also apply to general WAL when archive_mdoe
>> is on. Do we optimize for that?
>
> Hmm, no we don't. We do take that into account so that we refrain from
> issuing posix_fadvice(DONTNEED) if archive_mode is on, but we don't
> disable O_DIRECT. Maybe we should..

Since the performance of WAL write is more important than that of WAL
archiving in general, that optimization might offer little benefit.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

• Re: Streaming replication on win32, still broken at 2010-02-18 10:04:56 from Heikki Linnakangas

Responses

• Re: Streaming replication on win32, still broken at 2010-02-18 11:14:50 from Magnus Hagander

pgsql-hackers by date

Next:	From: Heikki Linnakangas	Date: 2010-02-18 11:14:15
	Subject: Re: Streaming replication and unfit messages
Previous:	From: Fujii Masao	Date: 2010-02-18 10:31:01
	Subject: Re: Streaming replication and unfit messages