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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_standby could not open wal file after selecting new timeline
Дата
Msg-id 279.1225908005@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pg_standby could not open wal file after selecting new timeline  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: pg_standby could not open wal file after selecting new timeline  (Dave Cramer <pg@fastcrypt.com>)
Список 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 по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: The suppress_redundant_updates_trigger() works incorrectly
Следующее
От: Tom Lane
Дата:
Сообщение: Re: The suppress_redundant_updates_trigger() works incorrectly