On Sat, Jul 30, 2005 at 12:06:11PM -0400, Alvaro Herrera wrote:
> On Sat, Jul 30, 2005 at 11:46:37AM -0400, Bruce Momjian wrote:
> > 
> > Updated patch applied.  Thanks.
> 
> Huh, something is very wrong with the markup:
> 
> http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-vacuum.html

This should fix it.  Sorry.

-- 
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Crear es tan difĂ­cil como ser libre" (Elsa Triolet)
Index: runtime.sgml
===================================================================
RCS file: /home/alvherre/cvs/pgsql/doc/src/sgml/runtime.sgml,v
retrieving revision 1.340
diff -c -r1.340 runtime.sgml
*** runtime.sgml        30 Jul 2005 15:17:18 -0000      1.340
--- runtime.sgml        30 Jul 2005 17:04:24 -0000
***************
*** 1380,1386 ****
      </sect3>
  
      <sect3 id="runtime-config-resource-vacuum-cost">
!      <title>Cost-Based Vacuum Delay</title>
  
       <para>
        During the execution of <xref linkend="sql-vacuum"
--- 1380,1388 ----
      </sect3>
  
      <sect3 id="runtime-config-resource-vacuum-cost">
!      <title id="runtime-config-resource-vacuum-cost-title">
!        Cost-Based Vacuum Delay
!      </title>
  
       <para>
        During the execution of <xref linkend="sql-vacuum"
Index: ref/vacuum.sgml
===================================================================
RCS file: /home/alvherre/cvs/pgsql/doc/src/sgml/ref/vacuum.sgml,v
retrieving revision 1.37
diff -c -r1.37 vacuum.sgml
*** ref/vacuum.sgml     30 Jul 2005 15:45:49 -0000      1.37
--- ref/vacuum.sgml     30 Jul 2005 17:04:40 -0000
***************
*** 180,186 ****
      increase in I/O traffic, which cause poor performance for other active
      sessions.  Therefore, it is sometimes advisable to use
      the cost-based vacuum delay feature.  See <xref
!     linkend="runtime" endterm="runtime-config-resource-vacuum-cost"> for more
      details.
     </para>
   </refsect1>
--- 180,186 ----
      increase in I/O traffic, which cause poor performance for other active
      sessions.  Therefore, it is sometimes advisable to use
      the cost-based vacuum delay feature.  See <xref
!     linkend="runtime" endterm="runtime-config-resource-vacuum-cost-title"> 
for more
      details.
     </para>
   </refsect1>
***************
*** 238,244 ****
  
    <simplelist type="inline">
     <member><xref linkend="app-vacuumdb" endterm="app-vacuumdb-title"></member>
!    <member><xref linkend="runtime" 
endterm="runtime-config-resource-vacuum-cost"></member>
    </simplelist>
   </refsect1>
  </refentry>
--- 238,244 ----
  
    <simplelist type="inline">
     <member><xref linkend="app-vacuumdb" endterm="app-vacuumdb-title"></member>
!    <member><xref linkend="runtime" 
endterm="runtime-config-resource-vacuum-cost-title"></member>
    </simplelist>
   </refsect1>
  </refentry>
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

Reply via email to