pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed"effective_io_concurrency" cannot be changed error when starting 8.4.2 instance
4+ messages / 3 participants
[nested] [flat]
* "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance
@ 2010-02-09 01:00 Kevin Kempter <kevink@consistentstate.com>
2010-02-09 01:11 ` Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Greg Stark <gsstark@mit.edu>
2010-02-09 01:13 ` Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 4+ messages in thread
From: Kevin Kempter @ 2010-02-09 01:00 UTC (permalink / raw)
To: pgsql-admin
Hi All;
I get the below error when trying to start an 8.4.2 instance
Anyone know what might be causing this?
FATAL: parameter "effective_io_concurrency" cannot be changed
Thanks in advance
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance
2010-02-09 01:00 "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Kevin Kempter <kevink@consistentstate.com>
@ 2010-02-09 01:11 ` Greg Stark <gsstark@mit.edu>
2010-02-09 01:36 ` Re: Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 1 reply; 4+ messages in thread
From: Greg Stark @ 2010-02-09 01:11 UTC (permalink / raw)
To: Kevin Kempter <kevink@consistentstate.com>; +Cc: pgsql-admin
On Tue, Feb 9, 2010 at 1:00 AM, Kevin Kempter
<kevink@consistentstate.com> wrote:
> I get the below error when trying to start an 8.4.2 instance
>
> Anyone know what might be causing this?
>
> FATAL: parameter "effective_io_concurrency" cannot be changed
>
What platform is this? Did you compile it yourself? What type of
system was it compiled on?
The error means that your system does not support the system interface
we need to support prefetching. In that case effective_io_concurrency
will be a read-only parameter set to 0 and any attempt to set it will
result in an error.
--
greg
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance
2010-02-09 01:00 "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Kevin Kempter <kevink@consistentstate.com>
2010-02-09 01:11 ` Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Greg Stark <gsstark@mit.edu>
@ 2010-02-09 01:36 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 2010-02-09 01:36 UTC (permalink / raw)
To: Greg Stark <gsstark@mit.edu>; +Cc: Kevin Kempter <kevink@consistentstate.com>; pgsql-admin
Greg Stark <gsstark@mit.edu> writes:
> The error means that your system does not support the system interface
> we need to support prefetching. In that case effective_io_concurrency
> will be a read-only parameter set to 0 and any attempt to set it will
> result in an error.
I wonder whether it would be better to have it still be a read-write
parameter, but with min/max values equal to zero. All the other cases
where we have read-only parameters, they're *always* read-only. It
seems a bit odd that this one is platform-specific not only as to the
allowed range but whether it can be assigned at all.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance
2010-02-09 01:00 "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Kevin Kempter <kevink@consistentstate.com>
@ 2010-02-09 01:13 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 4+ messages in thread
From: Tom Lane @ 2010-02-09 01:13 UTC (permalink / raw)
To: Kevin Kempter <kevink@consistentstate.com>; +Cc: pgsql-admin
Kevin Kempter <kevink@consistentstate.com> writes:
> I get the below error when trying to start an 8.4.2 instance
> Anyone know what might be causing this?
> FATAL: parameter "effective_io_concurrency" cannot be changed
You're probably trying to set that on a platform that hasn't got the
necessary system calls to support it.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2010-02-09 01:36 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-02-09 01:00 "effective_io_concurrency" cannot be changed error when starting 8.4.2 instance Kevin Kempter <kevink@consistentstate.com>
2010-02-09 01:11 ` Greg Stark <gsstark@mit.edu>
2010-02-09 01:36 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-02-09 01:13 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox