On Wed, Feb 17, 2010 at 4:07 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Feb 17, 2010 at 3:03 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> In that case, O_DIRECT would be counterproductive, no? It maps to
>> FILE_FLAG_NOI_BUFFERING, which makes sure it doesn't go into the
>> cache. So the read in the startup proc is actually guaranteed to
>> reuqire a physical read - of something we just wrote, so it'll almost
>> certainly end up waiting for a rotation, no?
>> Seems like getting rid of O_DIRECT here is the right thing to do,
>> regardless of this.
> Agreed. I'll remove O_DIRECT from walreceiver.
Here is the patch to do that.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Boszormenyi Zoltan||Date: 2010-02-17 09:20:56|
|Subject: Re: NaN/Inf fix for ECPG|
|Previous:||From: Takahiro Itagaki||Date: 2010-02-17 08:43:19|
|Subject: Re: Re: [BUGS] BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION|