| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Josh Berkus <josh(at)agliodbs(dot)com>, Chander Ganesan <chander(at)otg-nc(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: We should Axe /contrib/start-scripts |
| Date: | 2009-08-25 19:54:06 |
| Message-ID: | 2058.1251230046@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-08-25 20:03:44 | Re: We should Axe /contrib/start-scripts |
| Previous Message | Chander Ganesan | 2009-08-25 19:53:15 | Re: We should Axe /contrib/start-scripts |