postgres.git / summary / log / commit / refs

commit    38de5aad54b3eb37981cacd391fcde82f86d00fb
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Aug 04 16:06:53 2011 +0000
First released in: 9.2.0, 9.0.5, 9.1.0

    In documentaiton, clarify which commands have reduced WAL volume for
    wal_level = minimum.
    
    Backpatch to 9.1 and 9.0.


 doc/src/sgml/config.sgml | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 4fadca955c3..b774e2a3328 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1451,11 +1451,18 @@ SET ENABLE_SEQSCAN TO OFF;
         This parameter can only be set at server start.
        </para>
        <para>
-        In <literal>minimal</> level, WAL-logging of some bulk operations, like
-        <command>CREATE INDEX</>, <command>CLUSTER</> and <command>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
-        <xref linkend="populate-pitr">). But minimal WAL does not contain
+        In <literal>minimal</> level, WAL-logging of some bulk
+        operations can be safely skipped, which can make those
+        operations much faster (see <xref linkend="populate-pitr">).
+        Operations in which this optimization can be applied include:
+        <simplelist>
+         <item>CREATE TABLE AS</item>
+         <item>CREATE INDEX</item>
+         <item>CLUSTER</item>
+         <item>COPY into tables that were created or truncated in the same
+         transaction
+        </simplelist>
+        But minimal WAL does not contain
         enough information to reconstruct the data from a base backup and the
         WAL logs, so either <literal>archive</> or <literal>hot_standby</>
         level must be used to enable


[parent: 4af43ee3f165]