Re: pg_standby could not open wal file after selecting new timeline - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: pg_standby could not open wal file after selecting new timeline
Date
Msg-id 8D8C8DAF-2C9A-452D-B301-2BFBE9331C1E@fastcrypt.com
Whole thread Raw
In response to Re: pg_standby could not open wal file after selecting new timeline  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5-Nov-08, at 1:00 PM, Tom Lane wrote:

> I wrote:
>> Huh, is it possible that Linux rejects O_SYNC for a file on ramdisk?
>
> I found this in the Fedora 9 manpage for open(2):
>
>       O_DIRECT support was added under Linux in kernel version  
> 2.4.10.  Older
>       Linux kernels simply ignore this flag.  Some filesystems may  
> not imple-
>       ment the flag and open() will fail with EINVAL if it is used.
>
> so it may not be ramdisk per se that's the issue, but the filesystem
> you're using on it.
>
> We set O_DIRECT along with O_SYNC whenever O_DIRECT is defined.  I
> wonder whether there's a need to make that decision more configurable.
>

fsync=off works fine if that helps


>             regards, tom lane



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: [WIP] In-place upgrade
Next
From: "Jonah H. Harris"
Date:
Subject: Re: broken URL in commitfest page