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

From Tom Lane
Subject Re: pg_standby could not open wal file after selecting new timeline
Date
Msg-id 279.1225908005@sss.pgh.pa.us
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>)
Responses Re: pg_standby could not open wal file after selecting new timeline  (Dave Cramer <pg@fastcrypt.com>)
List 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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: The suppress_redundant_updates_trigger() works incorrectly
Next
From: Tom Lane
Date:
Subject: Re: The suppress_redundant_updates_trigger() works incorrectly