I doubt this is really "a bug." This usually just means that the server
failed to start for some reason (port already in use, bad configuration,
etc.) Any startup problem with the database will result in this
However - what might could be addressed is that it is pretty difficult
to debug what is actually causing Postgres to not start. Is it logged
anywhere? Typically I debug this by switching to the postgres user and
trying to start pg_ctl manually, which will print out the problem. But
there's got to be a better way.
On Thu, 30 Nov 2006 13:33:34 GMT, "Ilia" <iluha(at)igchat(dot)com> said:
> The following bug has been logged online:
> Bug reference: 2795
> Logged by: Ilia
> Email address: iluha(at)igchat(dot)com
> PostgreSQL version: postgreSQL 8.1
> Operating system: windows server 2003 standart edition
> Description: can't start service postgre
> I successfully shut down PostgreSQL, but I can't start it.
> Error message:
> Service "Postgre SQL Database Server 8.1 " on "localhost" was started but
> was stopped soon.
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
In response to
pgsql-bugs by date
|Next:||From: Mischa Sandberg||Date: 2006-11-30 21:14:08|
|Subject: Bug? change from 8.0 to 8.2rc1 in checking default expressions|
|Previous:||From: Bradley Russell||Date: 2006-11-30 16:15:50|
|Subject: Re: fsync and semctl errors with 8.1.5/win32|