On 14 January 2013 15:29, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Tom Lane wrote: >> Peter Eisentraut <pete...@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?
I think --force would be the accepted way to ensure something happens as specified Mind you, I'm not sure I see the value in throwing an error if the server is in the desired state already. Who actually wants that behaviour? Can't we just change the behaviour? Existing scripts would still work, since we are simply skipping an error. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
