In documentaiton, clarify which commands have reduced WAL volume for

wal_level = minimum.

Backpatch to 9.1 and 9.0.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 32bccb41c9f3285729ab0c9466a2c4dcff114997..c7e9d176c17068f1359021a24417e70b9cd2bb66 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1416,11 +1416,18 @@ SET ENABLE_SEQSCAN TO OFF;
         This parameter can only be set at server start.
        
        
-        In minimal level, WAL-logging of some bulk operations, like
-        CREATE INDEX, CLUSTER and COPY on
-        a table that was created or truncated in the same transaction can be
-        safely skipped, which can make those operations much faster (see
-        ). But minimal WAL does not contain
+        In minimal level, WAL-logging of some bulk
+        operations can be safely skipped, which can make those
+        operations much faster (see ).
+        Operations in which this optimization can be applied include:
+        
+         CREATE TABLE AS
+         CREATE INDEX
+         CLUSTER
+         COPY into tables that were created or truncated in the same
+         transaction
+        
+        But minimal WAL does not contain
         enough information to reconstruct the data from a base backup and the
         WAL logs, so either archive or hot_standby
         level must be used to enable