Re: BUG #5118: start-status-insert-fatal

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: BUG #5118: start-status-insert-fatal
Дата
Msg-id 4AD6F989020000250002B9B1@gw.wicourts.gov
обсуждение исходный текст
Ответ на BUG #5118: start-status-insert-fatal  ("Gerhard Leykam" <gel123@sealsystems.de>)
Ответы Re: BUG #5118: start-status-insert-fatal  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #5117: Table type Function Bug when column dropped
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5118: start-status-insert-fatal