Re: "pg_ctl promote" exit status

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: "pg_ctl promote" exit status
Date: 2013-01-28 09:18:25
Message-ID: 51064261.3000806@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26.01.2013 23:44, Aaron W. Swenson wrote:
> On Fri, Jan 25, 2013 at 01:54:06PM -0500, Peter Eisentraut wrote:
>> On 1/12/13 3:30 PM, Aaron W. Swenson wrote:
>>> The Linux Standard Base Core Specification 3.1 says this should return
>>> '3'. [1]
>>>
>>> [1] http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
>>
>> The LSB spec doesn't say anything about a "promote" action.
>>
>> And for the stop and reload actions that you tried to change, 3 is
>> "unimplemented".
>>
>> There is an ongoing discussion about the exit status of the stop action
>> under<https://commitfest.postgresql.org/action/patch_view?id=1045>, so
>> let's keep this item about the "promote" action.
>
> You are right. Had I read a little further down, it seems that the
> exit status should actually be 7.

Not sure if that LSB section is relevant anyway. It specifies the exit
codes for init scripts, but pg_ctl is not an init script.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2013-01-28 09:45:10 Re: Review of "pg_basebackup and pg_receivexlog to use non-blocking socket communication", was: Re: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous Message Heikki Linnakangas 2013-01-28 09:04:22 Re: unlogged tables vs. GIST