Skip site navigation (1) Skip section navigation (2)

Re: We should Axe /contrib/start-scripts

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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:34:28
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
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 DunstanDate: 2009-08-25 19:46:31
Subject: Re: We should Axe /contrib/start-scripts
Previous:From: Alvaro HerreraDate: 2009-08-25 19:02:53
Subject: Re: SET syntax in INSERT

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group