From: Robert Haas Date: Wed, 19 Oct 2011 00:13:27 +0000 (-0400) Subject: Make the CHECKPOINT reference page more clear. X-Git-Tag: REL9_2_BETA1~960 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c53d3a9ee1b1c85c7d905fb8ca80d327a55f1dfb;p=postgresql Make the CHECKPOINT reference page more clear. Josh Kupershmidt, reviewed by Fujii Masao --- diff --git a/doc/src/sgml/ref/checkpoint.sgml b/doc/src/sgml/ref/checkpoint.sgml index 7ffd40a605..e70b8c8cb4 100644 --- a/doc/src/sgml/ref/checkpoint.sgml +++ b/doc/src/sgml/ref/checkpoint.sgml @@ -25,31 +25,31 @@ CHECKPOINT Description - - Write-Ahead Logging (WAL) puts a checkpoint in the transaction log - every so often. (To adjust the automatic checkpoint interval, see - the run-time configuration options - and .) The - CHECKPOINT command forces an immediate - checkpoint when the command is issued, without waiting for a - scheduled checkpoint. - - A checkpoint is a point in the transaction log sequence at which all data files have been updated to reflect the information in the log. All data files will be flushed to disk. Refer to - for more information about the WAL system. + for more details about what happens + during a checkpoint. + + + + The CHECKPOINT command forces an immediate + checkpoint when the command is issued, without waiting for a + regular checkpoint scheduled by the system (controlled by the settings in + ). + CHECKPOINT is not intended for use during normal + operation. If executed during recovery, the CHECKPOINT command - will force a restartpoint rather than writing a new checkpoint. + will force a restartpoint (see ) + rather than writing a new checkpoint. - Only superusers can call CHECKPOINT. The command is - not intended for use during normal operation. + Only superusers can call CHECKPOINT.