From 05cd12ed5bc74c853a161c5a138a0cb6f9b0cb8a Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 13 Jan 2017 12:00:00 -0500 Subject: pg_ctl: Change default to wait for all actions The different actions in pg_ctl had different defaults for -w and -W, mostly for historical reasons. Most users will want the -w behavior, so make that the default. Remove the -w option in most example and test code, so avoid confusion and reduce verbosity. pg_upgrade is not touched, so it can continue to work with older installations. Reviewed-by: Beena Emerson Reviewed-by: Ryan Murphy --- doc/src/sgml/ref/pg_ctl-ref.sgml | 36 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml index 3f168005ec3..176dfaf98a3 100644 --- a/doc/src/sgml/ref/pg_ctl-ref.sgml +++ b/doc/src/sgml/ref/pg_ctl-ref.sgml @@ -31,7 +31,7 @@ PostgreSQL documentation pg_ctl - + seconds datadir @@ -60,7 +60,7 @@ PostgreSQL documentation pg_ctl - + seconds datadir @@ -91,7 +91,7 @@ PostgreSQL documentation pg_ctl - + seconds datadir @@ -117,7 +117,7 @@ PostgreSQL documentation - + seconds options @@ -391,17 +391,7 @@ PostgreSQL documentation Wait for an operation to complete. This is supported for the modes start, stop, restart, promote, - and register. - - - - Waiting is the default option for shutdowns, but not startups, - restarts, or promotions. This is mainly for historical reasons; the - waiting option is almost always preferable. If waiting is not - selected, the requested action is triggered, but there is no feedback - about its success. In that case, the server log file or an external - monitoring system would have to be used to check the progress and - success of the operation. + and register, and is the default for those modes. @@ -424,6 +414,18 @@ PostgreSQL documentation Do not wait for an operation to complete. This is the opposite of the option . + + + If waiting is disabled, the requested action is triggered, but there + is no feedback about its success. In that case, the server log file + or an external monitoring system would have to be used to check the + progress and success of the operation. + + + + In prior releases of PostgreSQL, this was the default except for + the stop mode. + @@ -593,7 +595,7 @@ PostgreSQL documentation To start the server, waiting until the server is accepting connections: -$ pg_ctl -w start +$ pg_ctl start @@ -637,7 +639,7 @@ PostgreSQL documentation To restart the server, waiting for it to shut down and restart: -$ pg_ctl -w restart +$ pg_ctl restart -- cgit v1.2.3