Re: pg_ctl idempotent option - Mailing list pgsql-hackers

From Dickson S. Guedes
Subject Re: pg_ctl idempotent option
Date
Msg-id CAHHcrert_1KPQ7yn=BNBg+0KUUpG9uOufoK=5i+90wtcx1i2YA@mail.gmail.com
Whole thread Raw
In response to Re: pg_ctl idempotent option  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2013/1/14 Tom Lane <tgl@sss.pgh.pa.us>:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> Tom Lane wrote:
>>> Peter Eisentraut <peter_e@gmx.net> writes:
>>>> Here is a patch to add an option -I/--idempotent to pg_ctl, the result
>>>> of which is that pg_ctl doesn't error on start or stop if the server is
>>>> already running or already stopped.
>
>>> Idempotent is a ten-dollar word.  Can we find something that average
>>> people wouldn't need to consult a dictionary to understand?
>
>> --no-error perhaps?
>
> Meh, that's probably going too far in the direction of imprecision.
> The point of this patch is that only very specific errors are
> suppressed.
>
> I don't have a better idea though.  It'd be easier if there were
> separate switches for the two cases, then you could call them
> --ok-if-running and --ok-if-stopped.  But that's not very workable,
> if only because both would want the same single-letter abbreviation.

--ignore-status
--ignore-status-start
--ignore-status-stop

?

Regards
-- 
Dickson S. Guedes
mail/xmpp: guedes@guedesoft.net - skype: guediz
http://guedesoft.net - http://www.postgresql.org.br



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: Vik Reykja
Date:
Subject: Re: pg_ctl idempotent option