Re: pgsql: In documentaiton, clarify which commands have reduced WAL volume

Alvaro Herrera wrote:
> Excerpts from Bruce Momjian's message of jue ago 04 12:07:15 -0400 2011:
> > In documentaiton, clarify which commands have reduced WAL volume for
> > wal_level = minimum.
> 
> Sorry that I misled you -- my tags were just an example, I wasn't trying
> to imply that the markup was correct.  (A quick make check would have
> told you as much).

I see.  :-(  Fixed with the attached patch and backpatched.  I added the
 tag as well.  It does seems  is best here.

-- 
  Bruce Momjian          http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
new file mode 100644
index b774e2a..33db25f
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** SET ENABLE_SEQSCAN TO OFF;
*** 1456,1466 ****
          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
--- 1456,1466 ----
          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