diff options
| author | Robert Haas <rhaas@postgresql.org> | 2011-11-07 12:27:26 -0500 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2011-11-07 12:27:26 -0500 |
| commit | bd2396988a1afbcb6424700e52a62f34d2951bdd (patch) | |
| tree | 4ecaf7b6527a43c0bdbb30f535cbbd585c8fb77d | |
| parent | ced3a93ccbbd0a3866f2324662f7a1fa4c31909a (diff) | |
| download | postgresql-bd2396988a1afbcb6424700e52a62f34d2951bdd.tar.gz postgresql-bd2396988a1afbcb6424700e52a62f34d2951bdd.zip | |
Minor grammar improvements.
| -rw-r--r-- | doc/src/sgml/wal.sgml | 6 |
1 files 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> |