A GUC variable in runtime.sgml had the wrong markup -- this patch
fixes that, and makes a few other tiny SGML improvements.
-Neil
Index: doc/src/sgml/runtime.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/runtime.sgml,v
retrieving revision 1.224
diff -c -r1.224 runtime.sgml
*** doc/src/sgml/runtime.sgml 1 Dec 2003 22:07:56 -0000 1.224
--- doc/src/sgml/runtime.sgml 4 Dec 2003 18:40:57 -0000
***************
*** 830,836 ****
server. The default is typically 1000, but may be less if your
kernel settings will not support it (as determined during
<application>initdb</>). Each buffer is 8192 bytes, unless a
! different value of <literal>BLCKSZ</> was chosen when building
the server. This setting must be at least 16, as well as at
least twice the value of <varname>max_connections</varname>;
however, settings significantly higher than the minimum are
--- 830,836 ----
server. The default is typically 1000, but may be less if your
kernel settings will not support it (as determined during
<application>initdb</>). Each buffer is 8192 bytes, unless a
! different value of <constant>BLCKSZ</constant> was chosen when building
the server. This setting must be at least 16, as well as at
least twice the value of <varname>max_connections</varname>;
however, settings significantly higher than the minimum are
***************
*** 2538,2548 ****
Turns on various assertion checks. This is a debugging aid. If
you are experiencing strange problems or crashes you might want
to turn this on, as it might expose programming mistakes. To use
! this option, the macro <literal>USE_ASSERT_CHECKING</literal>
must be defined when <productname>PostgreSQL</productname> is
built (accomplished by the <command>configure</command> option
<option>--enable-cassert</option>). Note that
! <literal>DEBUG_ASSERTIONS</literal> defaults to on if
<productname>PostgreSQL</productname> has been built with
assertions enabled.
</para>
--- 2538,2548 ----
Turns on various assertion checks. This is a debugging aid. If
you are experiencing strange problems or crashes you might want
to turn this on, as it might expose programming mistakes. To use
! this option, the macro <constant>USE_ASSERT_CHECKING</constant>
must be defined when <productname>PostgreSQL</productname> is
built (accomplished by the <command>configure</command> option
<option>--enable-cassert</option>). Note that
! <varname>debug_assertions</varname> defaults to on if
<productname>PostgreSQL</productname> has been built with
assertions enabled.
</para>
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
