On Wed, Oct 17, 2012 at 5:33 AM, Dhruv Ahuja <dhruvahuja(at)gmail(dot)com> wrote:
> The "pg_ctl promote" command returns an exit code of 1 when the server
> is not in standby mode, and the same exit code of 1 when the server
> isn't started at all. The only difference at the time being is the
> string output at the time, which FYI are...
> pg_ctl: cannot promote server; server is not in standby mode
> pg_ctl: PID file "/var/lib/pgsql/9.1/data/postmaster.pid" does not exist
> Is server running?
> I am in the process of developing a clustering solution around luci
> and rgmanager (in Red Hat EL 6) and for the time being, am basing it
> off the string output. Maybe each different exit reason should have a
> unique exit code, whatever my logic and approach to solving this
> problem be?
I suggest reposting this on pgsql-hackers. This mailing list is mostly dead.
The Enterprise PostgreSQL Company
 with apologies to S. Morgenstern
In response to
pgsql-cluster-hackers by date
|Next:||From: Henning Mälzer||Date: 2012-11-23 14:17:59|
|Subject: Question: Can i cut NON-HOT chain Pointers if there are no concurrent
|Previous:||From: Dhruv Ahuja||Date: 2012-10-17 09:33:51|
|Subject: "pg_ctl promote" exit status|