From bd2396988a1afbcb6424700e52a62f34d2951bdd Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Mon, 7 Nov 2011 12:27:26 -0500
Subject: [PATCH] Minor grammar improvements.
---
doc/src/sgml/wal.sgml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 3b86a4e1116..843d5c88805 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -424,13 +424,13 @@
linkend="guc-checkpoint-segments"> log segments, or every <xref
linkend="guc-checkpoint-timeout"> seconds, whichever comes first.
The default settings are 3 segments and 300 seconds (5 minutes), respectively.
- In cases where there are little or no writes to the WAL, checkpoints will be
+ In cases where little or no WAL has been written, checkpoints will be
skipped even if checkpoint_timeout has passed. At least one new WAL segment
must have been created before an automatic checkpoint occurs. The time
between checkpoints and when new WAL segments are created are not related
in any other way. If file-based WAL shipping is being used and you want to
- bound how often files are sent to standby server, to reduce potential data
- loss you should adjust archive_timeout parameter rather than the checkpoint
+ bound how often files are sent to standby server to reduce potential data
+ loss, you should adjust archive_timeout parameter rather than the checkpoint
parameters. It is also possible to force a checkpoint by using the SQL
command <command>CHECKPOINT</command>.
</para>
--
GitLab