1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>17.15.Developer Options</title>
<link rel="stylesheet" href="stylesheet.css" type="text/css">
<link rev="made" href="pgsql-docs@postgresql.org">
<meta name="generator" content="DocBook XSL Stylesheets V1.70.0">
<link rel="start" href="index.html" title="PostgreSQL 8.1.4 Documentation">
<link rel="up" href="runtime-config.html" title="Chapter17.Server Configuration">
<link rel="prev" href="runtime-config-custom.html" title="17.14.Customized Options">
<link rel="next" href="runtime-config-short.html" title="17.16.Short Options">
<link rel="copyright" href="ln-legalnotice.html" title="Legal Notice">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="runtime-config-developer"></a>17.15.Developer Options</h2></div></div></div>
<p> The following options are intended for work on the
<span class="productname">PostgreSQL</span> source, and in some cases
to assist with recovery of severely damaged databases. There
should be no reason to use them in a production database setup.
As such, they have been excluded from the sample
<code class="filename">postgresql.conf</code> file. Note that many of these
options require special source compilation flags to work at all.
</p>
<div class="variablelist"><dl>
<dt>
<a name="guc-debug-assertions"></a><span class="term"><code class="varname">debug_assertions</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> 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 <code class="symbol">USE_ASSERT_CHECKING</code>
must be defined when <span class="productname">PostgreSQL</span> is
built (accomplished by the <code class="command">configure</code> option
<code class="option">--enable-cassert</code>). Note that
<code class="varname">debug_assertions</code> defaults to <code class="literal">on</code>
if <span class="productname">PostgreSQL</span> has been built with
assertions enabled.
</p></dd>
<dt>
<a name="guc-pre-auth-delay"></a><span class="term"><code class="varname">pre_auth_delay</code> (<code class="type">integer</code>)</span>
</dt>
<dd><p> If nonzero, a delay of this many seconds occurs just after a new
server process is forked, before it conducts the authentication
process. This is intended to give an opportunity to attach to the
server process with a debugger to trace down misbehavior in
authentication.
</p></dd>
<dt>
<a name="guc-trace-notify"></a><span class="term"><code class="varname">trace_notify</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> Generates a great amount of debugging output for the
<code class="command">LISTEN</code> and <code class="command">NOTIFY</code>
commands. <a href="runtime-config-logging.html#guc-client-min-messages">client_min_messages</a> or
<a href="runtime-config-logging.html#guc-log-min-messages">log_min_messages</a> must be
<code class="literal">DEBUG1</code> or lower to send this output to the
client or server log, respectively.
</p></dd>
<dt>
<a name="guc-trace-sort"></a><span class="term"><code class="varname">trace_sort</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> If on, emit information about resource usage during sort operations.
This option is only available if the <code class="symbol">TRACE_SORT</code> macro
was defined when <span class="productname">PostgreSQL</span> was compiled.
(However, <code class="symbol">TRACE_SORT</code> is currently defined by default.)
</p></dd>
<dt>
<span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">trace_locks</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">trace_lwlocks</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">trace_userlocks</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">trace_lock_oidmin</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">trace_lock_table</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span xmlns="http://www.w3.org/TR/xhtml1/transitional" class="term"><code xmlns="" class="varname">debug_deadlocks</code> (<code xmlns="" class="type">boolean</code>)</span><br xmlns="http://www.w3.org/TR/xhtml1/transitional"></br><span class="term"><code class="varname">log_btree_build_stats</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> Various other code tracing and debugging options.
</p></dd>
<dt>
<a name="guc-wal-debug"></a><span class="term"><code class="varname">wal_debug</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> If on, emit WAL-related debugging output. This option is
only available if the <code class="symbol">WAL_DEBUG</code> macro was
defined when <span class="productname">PostgreSQL</span> was
compiled.
</p></dd>
<dt>
<a name="guc-zero-damaged-pages"></a><span class="term"><code class="varname">zero_damaged_pages</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> Detection of a damaged page header normally causes
<span class="productname">PostgreSQL</span> to report an error, aborting the current
command. Setting <code class="varname">zero_damaged_pages</code> to on causes
the system to instead report a warning, zero out the damaged page,
and continue processing. This behavior <span class="emphasis"><em>will destroy data</em></span>,
namely all the rows on the damaged page. But it allows you to get
past the error and retrieve rows from any undamaged pages that may
be present in the table. So it is useful for recovering data if
corruption has occurred due to hardware or software error. You should
generally not set this on until you have given up hope of recovering
data from the damaged page(s) of a table. The
default setting is <code class="literal">off</code>, and it can only be changed
by a superuser.
</p></dd>
</dl></div>
</div></body>
</html>
|
