bad posix_fadvise support causes initdb to exit ungracefully

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема bad posix_fadvise support causes initdb to exit ungracefully
Дата
Msg-id BANLkTim-M0iXXmW4kZKsuKue=OUibV38-Q@mail.gmail.com
обсуждение исходный текст
Ответы Re: bad posix_fadvise support causes initdb to exit ungracefully  (Merlin Moncure <mmoncure@gmail.com>)
Re: bad posix_fadvise support causes initdb to exit ungracefully  (PostgreSQL - Hans-Jürgen Schönig<postgres@cybertec.at>)
Re: bad posix_fadvise support causes initdb to exit ungracefully  (Peter Geoghegan <peter@2ndquadrant.com>)
Re: bad posix_fadvise support causes initdb to exit ungracefully  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Due to unfortunate environmental conditions (don't ask) I've been
trying to get postgres 9.0 up and running on a fairly ancient linux --
redhat EL 3 which as kernel 2.4.21.   initdb borks on the create
database step with the error message "child process exited with error
code 139".  A bit of tracing revealed the exit was happening at the
pg_flush_data which basically wraps posix_fadvise.   Disabling fadvise
support in pg_config_manual.h fixed the problem.

Things brings up a couple of questions:
*) Are linuxes this old out of support?
*) Should configure be testing for working posix_fadvise?

merlin


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Small SSI issues
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_upgrade using appname to lock out other users