On Tue, Oct 23, 2012 at 12:29:11PM -0400, Robert Haas wrote:
> On Tue, Oct 23, 2012 at 6:39 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
> > ...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?
The Linux Standard Base Core Specification 3.1 says this should return
Mr. Aaron W. Swenson
Gentoo Linux Developer
Email : titanofold(at)gentoo(dot)org
GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0
GnuPG ID : D1BBFDA0
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2013-01-12 20:39:16|
|Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)|
|Previous:||From: Heikki Linnakangas||Date: 2013-01-12 20:14:21|
|Subject: Re: [PATCH] unified frontend support for pg_malloc et al
and palloc/pfree mulation (was xlogreader-v4)|