Skip site navigation (1) Skip section navigation (2)

Re: posix_fadvise v22

From: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Postgres <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: posix_fadvise v22
Date: 2009-01-02 04:49:57
Message-ID: 262184F8-1206-4E2C-B50F-9FF84E63C1B6@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Sorry for top-posting -- phone mail client sucks.

I thought the autoconf ac_run_check was the test that people were  
questioning. That calls posix_fadvise to see if it crashes at  
configure time.

The guc run-time check is checking for known-buggy versions of glibc  
using sysconf to check what version of glibc you have.

-- 
Greg


On 1 Jan 2009, at 23:11, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:

>> Now that there's an actual run-time sysconf check for the buggy  
>> glibc called
>> by the guc function we arguably don't need the autoconf check_run  
>> check
>> anymore anyways.
>
> Isn't that the check I just removed for you, or are you talking about
> some other check that can also be removed?
>
> ...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-01-02 05:12:50
Subject: Re: posix_fadvise v22
Previous:From: Alex HunsakerDate: 2009-01-02 04:49:55
Subject: Re: Significantly larger toast tables on 8.4?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group