|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.391 2007/12/1713:54:10 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.392 2007/12/1714:00:52 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime"> |
4 | 4 | <title>Operating System Environment</title> |
@@ -1351,11 +1351,8 @@ sysctl -w vm.overcommit_memory=2 |
1351 | 1351 | <para> |
1352 | 1352 | The <xref linkend="app-pg-ctl"> program provides a convenient |
1353 | 1353 | interface for sending these signals to shut down the server. |
1354 | | - </para> |
1355 | | - |
1356 | | - <para> |
1357 | 1354 | Alternatively, you can send the signal directly using <command>kill</> |
1358 | | -(or <command>pg_ctl kill TERM [process id]</>on<productname>Windows</>). |
| 1355 | + onnon-Windows systems. |
1359 | 1356 | The <acronym>PID</> of the <command>postgres</command> process can be |
1360 | 1357 | found using the <command>ps</command> program, or from the file |
1361 | 1358 | <filename>postmaster.pid</filename> in the data directory. For |
|