Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm. As stated, I would expect pg_ctl to make it worse.
I've been playing with this, and I think the problem was that we
wanted a non-zero exit from the script if the start failed. That's
trivial with pg_ctl -w but not running postgres directly. I guess I
could run pg_ctl status in a loop after the start.
The reason is that we don't want certain other processes attempting to
start until and unless the database they use has started successfully.
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2009-08-25 19:46:31|
|Subject: Re: We should Axe /contrib/start-scripts|
|Previous:||From: Alvaro Herrera||Date: 2009-08-25 19:02:53|
|Subject: Re: SET syntax in INSERT|