Re: [SPAM] Re: posix_fadvise v22 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [SPAM] Re: posix_fadvise v22
Date
Msg-id 603c8f070901101107m3321d2acu439cea602d6c7a1c@mail.gmail.com
Whole thread Raw
In response to Re: [SPAM] Re: posix_fadvise v22  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I think at a minimum there should be a manual configuration switch
> (ie something in pg_config_manual.h) to allow the builder to disable
> use of posix_fadvise, even if configure thinks it's there.  Depending
> on buildfarm results we may have to do more than that.

This seems pretty pointless, since there is already a GUC to control
the behavior, and the default is off.  The only value here would be if
you could demonstrate that even with effective_io_concurrency set to 1
there is a significant performance dropoff.  But that would probably
be an argument for rejecting the patch outright, not adding a
compile-time switch.

...Robert


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [SPAM] Re: posix_fadvise v22
Next
From: Jeff Davis
Date:
Subject: Re: [PATCHES] updated hash functions for postgresql v1