Re: BUG #5660: Can't start db service if specify effective_io_concurrency
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #5660: Can't start db service if specify effective_io_concurrency |
| Дата | |
| Msg-id | 12182.1284647779@sss.pgh.pa.us обсуждение |
| Ответ на | BUG #5660: Can't start db service if specify effective_io_concurrency ("Mikio" <tkbysh2000@yahoo.co.jp>) |
| Ответы |
Re: BUG #5660: Can't start db service if specify effective_io_concurrency
|
| Список | pgsql-bugs |
"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 по дате отправления: