BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started - Mailing list pgsql-bugs

From Nacho Mezzadra
Subject BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started
Date
Msg-id 201102211554.p1LFsmnJ088295@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      5896
Logged by:          Nacho Mezzadra
Email address:      nachomezzadra@gmail.com
PostgreSQL version: 8.3.14-1
Operating system:   Red Hat 5.3 Enterprise
Description:        When server cannot be started, first it says that it
couldn't be started and then Server Started
Details:

When running the command service postgresql-8.3 start, and, lets say that
the port is already in use, and server cannot be started, then a message
comes up saying that the server could not be started (which is correct given
that the specified port was already in use), and right after that a message
says that PostgreSQL started successfully (which is obviously wrong).

Here is the output I get:

[root@RHEL53Nachao 40594]# service postgresql-8.3 start
Starting PostgreSQL 8.3:
waiting for server to
start...............................................................could
not start server
PostgreSQL 8.3 started successfully
[root@RHEL53Nachao 40594]#

pgsql-bugs by date:

Previous
From: Mark Kirkwood
Date:
Subject: Hung Vacuum in 8.3
Next
From: Maxim Boguk
Date:
Subject: Re: BUG #5798: Some weird error with pl/pgsql procedure