Re: pgsql: Re-enable the old code in xlog.c that tried to use

From: Gregory Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Postgres <pgsql-hackers(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Re-enable the old code in xlog.c that tried to use
Date: 2009-01-11 19:06:38
Message-ID: 877i51oe69.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


tgl(at)postgresql(dot)org (Tom Lane) writes:

> Log Message:
> -----------
> Re-enable the old code in xlog.c that tried to use posix_fadvise(), so that
> we can get some buildfarm feedback about whether that function is still
> problematic. (Note that the planned async-preread patch will not really
> prove anything one way or the other in buildfarm testing, since it will
> be inactive with default GUC settings.)

! #if defined(USE_POSIX_FADVISE) && defined(POSIX_FADV_DONTNEED)

I think if we're not putting the AC_CHECK_RUN check in then this should just
be HAVE_POSIX_FADVISE not USE_POSIX_FADVISE. The latter was the define I made
if the run check passed.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-01-11 19:22:00 Re: pgsql: Re-enable the old code in xlog.c that tried to use
Previous Message Tom Lane 2009-01-11 18:02:17 pgsql: Re-enable the old code in xlog.c that tried to use

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-11 19:14:50 Re: posix_fadvise v22
Previous Message Tom Lane 2009-01-11 18:02:17 pgsql: Re-enable the old code in xlog.c that tried to use