BUG #5118: start-status-insert-fatal

The following bug has been logged online:

Bug reference: 5118
Logged by: Gerhard Leykam
Email address: gel123(at)sealsystems(dot)de
PostgreSQL version: 8.4.0
Operating system: linux
Description: start-status-insert-fatal
Details:

Hi!

I am using a start script to set up my PostgreSQL database: it runs initdb,
if not done yet, starts the instance with pg_ctl start and checks everything
is fine by pg_ctl status.

If there is another PostgreSQL database on the same machine listening to the
same port, postmaster comes up, pg_ctl status says everthings fine, but
postmaster falls down with appropriate message in postgres.log.

All SQL commands in my script after status check are running against the
other database!

How do you think about some sort of postmaster.up file next to
postmaster.pid, which is created just as really everything is up and OK?

Regards,
Gerhard