From 3e4c6b542206bb95db499ddb4aa23b601d3c0acb Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 16 Dec 2007 10:17:13 +0000
Subject: [PATCH] Mention pg_ctl kill for Win32 in docs.
---
doc/src/sgml/runtime.sgml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 6500314c057..bd273c9e896 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.386 2007/11/28 15:42:31 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.387 2007/12/16 10:17:13 momjian Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
@@ -1350,7 +1350,8 @@ sysctl -w vm.overcommit_memory=2
</para>
<para>
- Alternatively, you can send the signal directly using <command>kill</>.
+ Alternatively, you can send the signal directly using <command>kill</>
+ (or <command>pg_ctl kill TERM [process id]</> on <productname>Windows</>).
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