/pgpatches/wal_level

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
new file mode 100644
index 4fadca9..a1f51ec
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** SET ENABLE_SEQSCAN TO OFF;
*** 1452,1461 ****
         </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
          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
--- 1452,1463 ----
         </para>
         <para>
          In <literal>minimal</> level, WAL-logging of some bulk operations, like
!         <command>CREATE INDEX</>, <command>CLUSTER</>, and <command>CREATE
!         TABLE AS</>, can be safely skipped, which can make those
!         operations much faster (see <xref linkend="populate-pitr">).
!         In minimal WAL-logging mode, it is also possible to skip WAL-logging of
!         and <command>COPY</> operations on 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 <literal>archive</> or <literal>hot_standby</>
          level must be used to enable