From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Reorder pg_ctl promote after pg_ctl status |
Date: | 2011-06-08 17:54:41 |
Message-ID: | E1QUMxl-0004vn-CT@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Reorder pg_ctl promote after pg_ctl status
Since start/stop/restart/reload/status is a kind of standard command
set, it seems odd to insert the special-purpose "promote" in between
the closely related "restart" and "reload". So put it after "status"
in code and documentation.
Put the documentation of the -U option in some sensible place.
Rewrite the synopsis sentence in help and documentation to make it
less of a growing mouthful.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/1bcdd66315fa1239793134e8284afc272f5975c3
Modified Files
--------------
doc/src/sgml/ref/pg_ctl-ref.sgml | 42 +++++++++---------
src/bin/pg_ctl/pg_ctl.c | 90 ++++++++++++++++++++------------------
2 files changed, 68 insertions(+), 64 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-08 19:25:17 | pgsql: Make citext's equality and hashing functions collation-insensiti |
Previous Message | Tom Lane | 2011-06-08 16:53:25 | pgsql: Allow domains over arrays to match ANYARRAY parameters again. |