From 59b1a23028245c593414c01ae482fc35709760ff Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 4 Dec 2003 21:24:56 +0000 Subject: [PATCH] Markup improvements --- doc/src/sgml/runtime.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 49bf3aa7af4..009fcfb8551 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -830,7 +830,7 @@ SET ENABLE_SEQSCAN TO OFF; server. The default is typically 1000, but may be less if your kernel settings will not support it (as determined during initdb). Each buffer is 8192 bytes, unless a - different value of BLCKSZ was chosen when building + different value of BLCKSZ was chosen when building the server. This setting must be at least 16, as well as at least twice the value of max_connections; however, settings significantly higher than the minimum are @@ -2538,11 +2538,11 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' 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 USE_ASSERT_CHECKING + this option, the macro USE_ASSERT_CHECKING must be defined when PostgreSQL is built (accomplished by the configure option ). Note that - DEBUG_ASSERTIONS defaults to on if + debug_assertions defaults to on if PostgreSQL has been built with assertions enabled. -- 2.39.5