Docs: modified gpstop options description
@@ -129,8 +129,13 @@ $ gpstart</codeblock>
<codeph>postgres</codeph> processes in the system, including the master and all segment
instances. The <codeph>gpstop</codeph> utility uses a default of up to 64 parallel worker
threads to bring down the Postgres instances that make up the Greenplum Database cluster.
- The system waits for any active transactions to finish before shutting down. To stop
- Greenplum Database immediately, use fast mode.</context>
+ The system waits for any active transactions to finish before shutting down. If after two
+ minutes there are still active connections, <codeph>gpstop</codeph> will prompt you to
+ either continue waiting in smart mode, stop in fast mode, or stop in immediate mode. To stop
+ Greenplum Database immediately, use fast mode. <note type="important">Immediate shut down
+ mode is not recommended. This mode kills all database processes without allowing the
+ database server to complete transaction processing or clean up any temporary or in-process
+ work files.</note></context>
<steps-unordered>
<step>
<cmd>To stop Greenplum Database:</cmd>
@@ -143,9 +148,10 @@ $ gpstart</codeblock>
<stepxmp>
<codeblock>$ gpstop -M fast</codeblock>
</stepxmp>
- <stepresult>By default, you are not allowed to shut down Greenplum Database if there are any
- client connections to the database. Use the <codeph>-M fast</codeph> option to roll
- back all in progress transactions and terminate any connections before shutting down.</stepresult>
+ <stepresult>By default, you are not allowed to shut down Greenplum Database if there are
+ any client connections to the database. Use the <codeph>-M fast</codeph> option to roll
+ back all in progress transactions and terminate any connections before shutting
+ down.</stepresult>
</step>
</steps-unordered>
</taskbody>
