Re: We should Axe /contrib/start-scripts
| От | Tom Lane |
|---|---|
| Тема | Re: We should Axe /contrib/start-scripts |
| Дата | |
| Msg-id | 2058.1251230046@sss.pgh.pa.us обсуждение |
| Ответ на | Re: We should Axe /contrib/start-scripts (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: We should Axe /contrib/start-scripts
Re: We should Axe /contrib/start-scripts |
| Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes:
> Here's a snippet from my F11 system:
> $SU -l postgres -c "$PGENGINE/postmaster -p '$PGPORT' -D
> '$PGDATA' ${PGOPTS} &" >> "$PGLOG" 2>&1 < /dev/null
> sleep 2
> pid=`pidof -s "$PGENGINE/postmaster"`
> if [ $pid ] && [ -f "$PGDATA/postmaster.pid" ]
> then
> success "$PSQL_START"
Of course, this is a complete kluge --- it assumes the postmaster will
create its pidfile in less than two seconds. And for that matter, it's
not very proof against the case of a pre-existing postmaster. But in
any case, it (intentionally) doesn't wait for the postmaster to be ready
to accept connections, so it's not solving Kevin's problem.
regards, tom lane
В списке pgsql-hackers по дате отправления: