Re: WAL documentation changes

Tatsuo Ishii wrote:
> Bruce,
>
> In your document change which one can be placed on non-journalling
> file system? data? wal? or both?

Both.  I have updated the docs to mention this, patch attached.
--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/wal.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v
retrieving revision 1.55
diff -c -c -r1.55 wal.sgml
*** doc/src/sgml/wal.sgml    10 Dec 2008 11:05:49 -0000    1.55
--- doc/src/sgml/wal.sgml    18 Dec 2008 22:15:53 -0000
***************
*** 138,145 ****
     <tip>
      <para>
       Because <acronym>WAL</acronym> restores database file
!      contents after a crash, it is not necessary to use a
!      journaled filesystem for reliability.  In fact, journaling
       overhead can reduce performance, especially if journaling
       causes file system <emphasis>data</emphasis> to be flushed
       to disk.  Fortunately, data flushing during journaling can
--- 138,145 ----
     <tip>
      <para>
       Because <acronym>WAL</acronym> restores database file
!      contents after a crash, journaled filesystems are necessary for
!      reliable storage of the data files or WAL files.  In fact, journaling
       overhead can reduce performance, especially if journaling
       causes file system <emphasis>data</emphasis> to be flushed
       to disk.  Fortunately, data flushing during journaling can