From 4f57c28da067d0df4a1a23e0d0bcd9aa14cd7c5e Mon Sep 17 00:00:00 2001
From: Magnus Hagander <magnus@hagander.net>
Date: Tue, 13 Apr 2010 08:19:12 +0000
Subject: [PATCH] Fix typo.

Fujii Masao
---
 doc/src/sgml/config.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index b65c336cc1..a548968b54 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.264 2010/04/12 22:09:58 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.265 2010/04/13 08:19:12 mha Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -1733,7 +1733,7 @@ SET ENABLE_SEQSCAN TO OFF;
         <varname>archive_mode</> is enabled, WAL archiving is temporarily
         disabled, but the server continues to accumulate WAL segment files in
         the expectation that a command will soon be provided.  Setting
-        <varname>archive_mode</> to a command that does nothing but
+        <varname>archive_command</> to a command that does nothing but
         return true, e.g. <literal>/bin/true</>, effectively disables
         archiving, but also breaks the chain of WAL files needed for
         archive recovery, so it should only be used in unusual circumstances.