Re: BUG #5118: start-status-insert-fatal - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #5118: start-status-insert-fatal
Date
Msg-id 4AD6F989020000250002B9B1@gw.wicourts.gov
Whole thread Raw
In response to BUG #5118: start-status-insert-fatal  ("Gerhard Leykam" <gel123@sealsystems.de>)
Responses Re: BUG #5118: start-status-insert-fatal
List pgsql-bugs
"Gerhard Leykam" <gel123@sealsystems.de> wrote:

> 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.

This is definitely not a PostgreSQL bug.

Perhaps the best place to start, before suggesting a new PostgreSQL
feature to solve this, would be to post to one of the other lists
(admin, maybe?) and describe what you are trying to accomplish with
your script, along with the problems you've found with your current
version of the script.  With a little more information, someone might
be able to suggest a solution.  (Since you're running on Linux,
something involving the lockfile utility might suffice.)

-Kevin

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #5117: Table type Function Bug when column dropped
Next
From: Tom Lane
Date:
Subject: Re: BUG #5118: start-status-insert-fatal