Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
59b1a230
Commit
59b1a230
authored
Dec 04, 2003
by
Peter Eisentraut
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Markup improvements
parent
6de3fe3c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
doc/src/sgml/runtime.sgml
doc/src/sgml/runtime.sgml
+4
-4
No files found.
doc/src/sgml/runtime.sgml
View file @
59b1a230
<!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.22
4 2003/12/01 22:07:56 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.22
5 2003/12/04 21:24:56 petere
Exp $
-->
<Chapter Id="runtime">
...
...
@@ -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
<application>initdb</>). Each buffer is 8192 bytes, unless a
different value of <
literal>BLCKSZ</
> was chosen when building
different value of <
symbol>BLCKSZ</symbol
> 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,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 <
literal>USE_ASSERT_CHECKING</litera
l>
this option, the macro <
symbol>USE_ASSERT_CHECKING</symbo
l>
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
<
varname>debug_assertions</varname
> defaults to on if
<productname>PostgreSQL</productname> has been built with
assertions enabled.
</para>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment