From cc04aaf9de48cc6246190b96310a669166cff29a Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 17 Dec 2007 14:00:52 +0000
Subject: [PATCH] Update pg_ctk/kill docs.
---
doc/src/sgml/runtime.sgml | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index c4b1eafd775..86555ba2bac 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.391 2007/12/17 13:54:10 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.392 2007/12/17 14:00:52 momjian Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
@@ -1351,11 +1351,8 @@ sysctl -w vm.overcommit_memory=2
<para>
The <xref linkend="app-pg-ctl"> program provides a convenient
interface for sending these signals to shut down the server.
- </para>
-
- <para>
Alternatively, you can send the signal directly using <command>kill</>
- (or <command>pg_ctl kill TERM [process id]</> on <productname>Windows</>).
+ on non-Windows systems.
The <acronym>PID</> of the <command>postgres</command> process can be
found using the <command>ps</command> program, or from the file
<filename>postmaster.pid</filename> in the data directory. For
--
GitLab