Skip site navigation (1) Skip section navigation (2)

BUG #5660: Can't start db service if specify effective_io_concurrency

From: "Mikio" <tkbysh2000(at)yahoo(dot)co(dot)jp>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5660: Can't start db service if specify effective_io_concurrency
Date: 2010-09-16 10:52:18
Message-ID: 201009161052.o8GAqInB041980@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5660
Logged by:          Mikio
Email address:      tkbysh2000(at)yahoo(dot)co(dot)jp
PostgreSQL version: 9.0 RC1
Operating system:   Windows XP SP3 Japanese
Description:        Can't start db service if specify
effective_io_concurrency
Details: 

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.
I looked a log file in pg_log directory, but no relative entries.
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ł܂

I changed the value from 10 to 1, but the symptom was same.
I commented the line out like as default, the service started up successful.

Responses

pgsql-bugs by date

Next:From: MikioDate: 2010-09-16 11:12:34
Subject: BUG #5661: The character encoding in logfile is confusing.
Previous:From: BERTRAND JoelDate: 2010-09-16 08:51:14
Subject: [8.4.4] Strange bus error on Solaris 10/sparc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group