Re: pg_standby could not open wal file after selecting new timeline

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_standby could not open wal file after selecting new timeline
Date: 2008-11-05 18:22:20
Message-ID: 8D8C8DAF-2C9A-452D-B301-2BFBE9331C1E@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2008-11-05 18:23:02 Re: broken URL in commitfest page
Previous Message Martijn van Oosterhout 2008-11-05 18:16:12 Re: [WIP] In-place upgrade