The following bug has been logged on the website:
Bug reference: 8079
Logged by: Christopher Bialas
Email address: krzbia@interia.pl
PostgreSQL version: 9.2.4
Operating system: Microsoft Windows 2008R2 Standard server
Description: =
With very high load of the server during startup (e.g. simultaneous logon
to local console) pg_ctl is being killed by windows service controller as it
does not respond on time. I've seen it with process explorer:
1. pg_ctl starts, then
2. postgres processing tasks start
3. pg_ctl is killed leaving postgres workers running.
As a result windows service is totally confused as service is dead, and it
cannot be started again as it finds out that postgres is already running.
The following is the excerpt from windows log:
<Event xmlns=3D"http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=3D"PostgreSQL" /> =
<EventID Qualifiers=3D"0">0</EventID> =
<Level>4</Level> =
<Task>0</Task> =
<Keywords>0x80000000000000</Keywords> =
<TimeCreated SystemTime=3D"2013-04-17T09:04:31.000000000Z" /> =
<EventRecordID>227797</EventRecordID> =
<Channel>Application</Channel> =
<Computer>mypc</Computer> =
<Security /> =
</System>
- <EventData>
<Data>Waiting for server startup...</Data> =
</EventData>
</Event>
=
- <Event xmlns=3D"http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=3D"PostgreSQL" /> =
<EventID Qualifiers=3D"0">0</EventID> =
<Level>2</Level> =
<Task>0</Task> =
<Keywords>0x80000000000000</Keywords> =
<TimeCreated SystemTime=3D"2013-04-17T09:04:36.000000000Z" /> =
<EventRecordID>227801</EventRecordID> =
<Channel>Application</Channel> =
<Computer>mypc</Computer> =
<Security /> =
</System>
- <EventData>
<Data>Timed out waiting for server startup</Data> =
</EventData>
</Event>
