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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Cramer <pg(at)fastcrypt(dot)com>, 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:00:05
Message-ID: 279.1225908005@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-05 18:10:35 Re: The suppress_redundant_updates_trigger() works incorrectly
Previous Message Andrew Dunstan 2008-11-05 17:56:01 Re: The suppress_redundant_updates_trigger() works incorrectly