Re: Unsupported effective_io_concurrency platforms - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Unsupported effective_io_concurrency platforms
Date
Msg-id 49C9FBD6.4060800@gmx.net
Whole thread Raw
In response to Re: Unsupported effective_io_concurrency platforms  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Unsupported effective_io_concurrency platforms  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Joshua D. Drake wrote:
> On Mon, 2009-03-23 at 16:21 -0400, Bruce Momjian wrote:
>> If a platform doesn't have posix_fadvise(), we don't allow
>> effective_io_concurrency to be set to anything but zero:
>>
>>     test=> set  effective_io_concurrency = 1;
>>     ERROR:  1 is outside the valid range for parameter "effective_io_concurrency" (0 .. 0)
>>     test=> set  effective_io_concurrency = 0;
>>     SET
>>
>> Do we want to give a more informative error message, like "not supported
>> on this platform?"
> 
> I would say so.

The trick will be to fit this into the GUC framework.


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: New trigger option of pg_standby
Next
From: Gurjeet Singh
Date:
Subject: Re: display previous query string of idle-in-transaction