summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-08-04 12:06:54 -0400
committerBruce Momjian <bruce@momjian.us>2011-08-04 12:06:54 -0400
commit072e6076d10955da5ee46416607a8ff19afd6b40 (patch)
treedab6029937bb8593b920bce50248ad34234d8626
parentd3061f036df68d4c495f6db79994b48725936241 (diff)
In documentaiton, clarify which commands have reduced WAL volume for
wal_level = minimum. Backpatch to 9.1 and 9.0.
-rw-r--r--doc/src/sgml/config.sgml17
1 files changed, 12 insertions, 5 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 32bccb41c9f..c7e9d176c17 100644
--- 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.
</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