From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Subject: | typo in config.sgml |
Date: | 2010-04-13 00:31:43 |
Message-ID: | k2g3f0b79eb1004121731vc38c6aacn3a154cc8fb9a57c8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hi,
I found the typo in config.sgml.
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 33d4e37..8d3c86b 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -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.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-04-13 08:19:23 | Re: typo in config.sgml |
Previous Message | Bruce Momjian | 2010-04-12 22:05:56 | Re: confusing archive_command example |