Re: Unsupported effective_io_concurrency platforms

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: jd(at)commandprompt(dot)com
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unsupported effective_io_concurrency platforms
Date: 2009-03-25 09:39:34
Message-ID: 49C9FBD6.4060800@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2009-03-25 09:59:37 Re: display previous query string of idle-in-transaction
Previous Message Fujii Masao 2009-03-25 09:32:12 Re: New trigger option of pg_standby