Re: "pg_ctl promote" exit status - Mailing list pgsql-hackers

From Robert Haas
Subject Re: "pg_ctl promote" exit status
Date
Msg-id CA+TgmoZY5L-tWo66qL74=1xON_yGsiLpMyMvuv64zBR0fysDhw@mail.gmail.com
Whole thread Raw
In response to "pg_ctl promote" exit status  (Dhruv Ahuja <dhruvahuja@gmail.com>)
Responses Re: "pg_ctl promote" exit status  ("Aaron W. Swenson" <titanofold@gentoo.org>)
Re: "pg_ctl promote" exit status  (Dhruv Ahuja <dhruvahuja@gmail.com>)
List pgsql-hackers
On Tue, Oct 23, 2012 at 6:39 AM, Dhruv Ahuja <dhruvahuja@gmail.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
>
> ...and...
>
> pg_ctl: PID file "/var/lib/pgsql/9.1/data/postmaster.pid" does not exist
> Is server running?
>
> ...respectively.
>
> 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?

That doesn't seem like a bad idea.  Got a patch?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Successor of MD5 authentication, let's use SCRAM
Next
From: Noah Misch
Date:
Subject: Re: Incorrect behaviour when using a GiST index on points