Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #5660: Can't start db service if specify effective_io_concurrency - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5660: Can't start db service if specify effective_io_concurrency
Date
Msg-id 12182.1284647779@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5660: Can't start db service if specify effective_io_concurrency  ("Mikio" <tkbysh2000@yahoo.co.jp>)
Responses Re: BUG #5660: Can't start db service if specify effective_io_concurrency  (tkbysh2000@yahoo.co.jp)
List pgsql-bugs
Tree view 
"Mikio" <tkbysh2000@yahoo.co.jp> writes:
> I'm using postgresql 9.0 rc1, and I specified 10 for
> effective_io_concurrency in postgresql.conf.
> I restarted postgresql windows service, but the service didn't start.

This is unsurprising: you can only set effective_io_concurrency on
platforms that have posix_fadvise(), which I rather doubt Windows does.

> I looked windows event viewer, I found an event from PostgreSQL, and it was
> below.(The characters in the message were broken.)

>> FATAL:  p[^"effective_io_concurrency"ύXł܂

Hm, what I get when I try that on a machine without posix_fadvise()
is

FATAL:  parameter "effective_io_concurrency" cannot be changed

I think you have some other configuration problem that's messing up
your log entries.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Re: BUG #5660: Can't start db service if specify effective_io_concurrency
Next
From: Robert Haas
Date:
Subject: Re: BUG #5650: Postgres service showing as stopped when in fact it is running