Re: bad posix_fadvise support causes initdb to exit ungracefully - Mailing list pgsql-hackers

From PostgreSQL - Hans-Jürgen Schönig
Subject Re: bad posix_fadvise support causes initdb to exit ungracefully
Date
Msg-id DA2CA723-EDCD-4469-9D98-F960B73C25CA@cybertec.at
Whole thread Raw
In response to bad posix_fadvise support causes initdb to exit ungracefully  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: bad posix_fadvise support causes initdb to exit ungracefully
List pgsql-hackers
hello ...

2.4? we know that some versions of 2.4 cause problems due to broken posix_fadvise. if i remember correctly we built
someconfigure magic into PostgreSQL to check for this bug. what does this check do? 
many thanks,
    hans



On Jun 15, 2011, at 6:12 PM, Merlin Moncure wrote:

> 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
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: procpid?
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: procpid?