Convert tabs to spaces in SGML.

doc/src/sgml/config.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.239 2009/12/19 01:32:31 sriggs Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.240 2009/12/19 17:49:50 momjian Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -1755,15 +1755,15 @@ archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"'  # Windows
       <term><varname>recovery_connections</varname> (<type>boolean</type>)</term>
       <listitem>
        <para>
-		Parameter has two roles. During recovery, specifies whether or not
-		you can connect and run queries to enable <xref linkend="hot-standby">.
-		During normal running, specifies whether additional information is written
-		to WAL to allow recovery connections on a standby server that reads
-		WAL data generated by this server. The default value is
+        Parameter has two roles. During recovery, specifies whether or not
+        you can connect and run queries to enable <xref linkend="hot-standby">.
+        During normal running, specifies whether additional information is written
+        to WAL to allow recovery connections on a standby server that reads
+        WAL data generated by this server. The default value is
         <literal>on</literal>.  It is thought that there is little
-		measurable difference in performance from using this feature, so
-		feedback is welcome if any production impacts are noticeable.
-		It is likely that this parameter will be removed in later releases.
+        measurable difference in performance from using this feature, so
+        feedback is welcome if any production impacts are noticeable.
+        It is likely that this parameter will be removed in later releases.
         This parameter can only be set at server start.
        </para>
       </listitem>
@@ -1773,15 +1773,15 @@ archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"'  # Windows
       <term><varname>max_standby_delay</varname> (<type>string</type>)</term>
       <listitem>
        <para>
-		When server acts as a standby, this parameter specifies a wait policy
-		for queries that conflict with incoming data changes. Valid settings
-		are -1, meaning wait forever, or a wait time of 0 or more seconds.
-		If a conflict should occur the server will delay up to this
-		amount before it begins trying to resolve things less amicably, as
-		described in <xref linkend="hot-standby-conflict">. Typically,
-		this parameter makes sense only during replication, so when
-		performing an archive recovery to recover from data loss a
-		parameter setting of 0 is recommended.  The default is 30 seconds.
+        When server acts as a standby, this parameter specifies a wait policy
+        for queries that conflict with incoming data changes. Valid settings
+        are -1, meaning wait forever, or a wait time of 0 or more seconds.
+        If a conflict should occur the server will delay up to this
+        amount before it begins trying to resolve things less amicably, as
+        described in <xref linkend="hot-standby-conflict">. Typically,
+        this parameter makes sense only during replication, so when
+        performing an archive recovery to recover from data loss a
+        parameter setting of 0 is recommended.  The default is 30 seconds.
         This parameter can only be set in the <filename>postgresql.conf</>
         file or on the server command line.
        </para>
@@ -4226,17 +4226,17 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
       <listitem>
        <para>
         Specifies the number of transactions by which <command>VACUUM</> and
-		<acronym>HOT</> updates will defer cleanup of dead row versions. The
-		default is 0 transactions, meaning that dead row versions will be
-		removed as soon as possible. You may wish to set this to a non-zero
-		value when planning or maintaining a <xref linkend="hot-standby">
-		configuration. The recommended value is <literal>0</> unless you have
-		clear reason to increase it. The purpose of the parameter is to
-		allow the user to specify an approximate time delay before cleanup
-		occurs. However, it should be noted that there is no direct link with
-		any specific time delay and so the results will be application and
-		installation specific, as well as variable over time, depending upon
-		the transaction rate (of writes only).
+        <acronym>HOT</> updates will defer cleanup of dead row versions. The
+        default is 0 transactions, meaning that dead row versions will be
+        removed as soon as possible. You may wish to set this to a non-zero
+        value when planning or maintaining a <xref linkend="hot-standby">
+        configuration. The recommended value is <literal>0</> unless you have
+        clear reason to increase it. The purpose of the parameter is to
+        allow the user to specify an approximate time delay before cleanup
+        occurs. However, it should be noted that there is no direct link with
+        any specific time delay and so the results will be application and
+        installation specific, as well as variable over time, depending upon
+        the transaction rate (of writes only).
        </para>
       </listitem>
      </varlistentry>

doc/src/sgml/func.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.494 2009/12/19 01:32:31 sriggs Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.495 2009/12/19 17:49:50 momjian Exp $ -->
 
  <chapter id="functions">
   <title>Functions and Operators</title>
@@ -13139,7 +13139,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
    <para>
     The functions shown in <xref
     linkend="functions-recovery-info-table"> provide information
-	about the current status of Hot Standby.
+    about the current status of Hot Standby.
     These functions may be executed during both recovery and in normal running.
    </para>
 
@@ -13158,7 +13158,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
         </entry>
        <entry><type>bool</type></entry>
        <entry>True if recovery is still in progress.
-	   </entry>
+       </entry>
       </row>
      </tbody>
     </tgroup>