From 2f67722dda9a46e82bad6807a12401dd7839910c Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 16 Feb 2008 21:14:08 +0000
Subject: [PATCH] No need to use checkpoint_warning to log checkpoints --- we
added log_checkpoints in 8.3.
---
doc/src/sgml/config.sgml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 68ee06fae03..ceaeb205d91 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.165 2008/02/16 21:11:32 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.166 2008/02/16 21:14:08 momjian Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@@ -1638,9 +1638,6 @@ SET ENABLE_SEQSCAN TO OFF;
30 seconds (<literal>30s</>). Zero disables the warning.
This parameter can only be set in the <filename>postgresql.conf</>
file or on the server command line.
- (Set it to a value greater than <varname>checkpoint_timeout</> to
- log all checkpoints. Of course, the warning suggesting increasing
- <varname>checkpoint_segments</> should be ignored.)
</para>
</listitem>
</varlistentry>
--
GitLab