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
100
101
102
103
104
105
106
107
108
109
110
111
112
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>17.13.Preset 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-compatible.html" title="17.12.Version and Platform Compatibility">
<link rel="next" href="runtime-config-custom.html" title="17.14.Customized 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-preset"></a>17.13.Preset Options</h2></div></div></div>
<p> The following “<span class="quote">parameters</span>” are read-only, and are determined
when <span class="productname">PostgreSQL</span> is compiled or when it is
installed. As such, they have been excluded from the sample
<code class="filename">postgresql.conf</code> file. These options report
various aspects of <span class="productname">PostgreSQL</span> behavior
that may be of interest to certain applications, particularly
administrative front-ends.
</p>
<div class="variablelist"><dl>
<dt>
<a name="guc-block-size"></a><span class="term"><code class="varname">block_size</code> (<code class="type">integer</code>)</span>
</dt>
<dd><p> Reports the size of a disk block. It is determined by the value
of <code class="literal">BLCKSZ</code> when building the server. The default
value is 8192 bytes. The meaning of some configuration
variables (such as <a href="runtime-config-resource.html#guc-shared-buffers">shared_buffers</a>) is
influenced by <code class="varname">block_size</code>. See <a href="runtime-config-resource.html" title="17.4.Resource Consumption">Section17.4, “Resource Consumption”</a> for information.
</p></dd>
<dt>
<a name="guc-integer-datetimes"></a><span class="term"><code class="varname">integer_datetimes</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> Reports whether <span class="productname">PostgreSQL</span> was built
with support for 64-bit-integer dates and times. It is set by
configuring with <code class="literal">--enable-integer-datetimes</code>
when building <span class="productname">PostgreSQL</span>. The
default value is <code class="literal">off</code>.
</p></dd>
<dt>
<a name="guc-lc-collate"></a><span class="term"><code class="varname">lc_collate</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Reports the locale in which sorting of textual data is done.
See <a href="charset.html#locale" title="21.1.Locale Support">Section21.1, “Locale Support”</a> for more information.
The value is determined when the database cluster is initialized.
</p></dd>
<dt>
<a name="guc-lc-ctype"></a><span class="term"><code class="varname">lc_ctype</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Reports the locale that determines character classifications.
See <a href="charset.html#locale" title="21.1.Locale Support">Section21.1, “Locale Support”</a> for more information.
The value is determined when the database cluster is initialized.
Ordinarily this will be the same as <code class="varname">lc_collate</code>,
but for special applications it might be set differently.
</p></dd>
<dt>
<a name="guc-max-function-args"></a><span class="term"><code class="varname">max_function_args</code> (<code class="type">integer</code>)</span>
</dt>
<dd><p> Reports the maximum number of function arguments. It is determined by
the value of <code class="literal">FUNC_MAX_ARGS</code> when building the server. The
default value is 100.
</p></dd>
<dt>
<a name="guc-max-identifier-length"></a><span class="term"><code class="varname">max_identifier_length</code> (<code class="type">integer</code>)</span>
</dt>
<dd><p> Reports the maximum identifier length. It is determined as one
less than the value of <code class="literal">NAMEDATALEN</code> when building
the server. The default value of <code class="literal">NAMEDATALEN</code> is
64; therefore the default
<code class="varname">max_identifier_length</code> is 63.
</p></dd>
<dt>
<a name="guc-max-index-keys"></a><span class="term"><code class="varname">max_index_keys</code> (<code class="type">integer</code>)</span>
</dt>
<dd><p> Reports the maximum number of index keys. It is determined by
the value of <code class="literal">INDEX_MAX_KEYS</code> when building the server. The
default value is 32.
</p></dd>
<dt>
<a name="guc-server-encoding"></a><span class="term"><code class="varname">server_encoding</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Reports the database encoding (character set).
It is determined when the database is created. Ordinarily,
clients need only be concerned with the value of <a href="runtime-config-client.html#guc-client-encoding">client_encoding</a>.
</p></dd>
<dt>
<a name="guc-server-version"></a><span class="term"><code class="varname">server_version</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Reports the version number of the server. It is determined by the
value of <code class="literal">PG_VERSION</code> when building the server.
</p></dd>
<dt>
<a name="guc-standard-conforming-strings"></a><span class="term"><code class="varname">standard_conforming_strings</code> (<code class="type">boolean</code>)</span>
</dt>
<dd><p> Reports whether ordinary string literals
(<code class="literal">'...'</code>) treat backslashes literally, as specified in
the SQL standard. The value is currently always <code class="literal">off</code>,
indicating that backslashes are treated as escapes. It is planned
that this will change to <code class="literal">on</code> in a future
<span class="productname">PostgreSQL</span> release when string literal
syntax changes to meet the standard. Applications may check this
parameter to determine how string literals will be processed.
The presence of this parameter can also be taken as an indication
that the escape string syntax (<code class="literal">E'...'</code>) is supported.
</p></dd>
</dl></div>
</div></body>
</html>
|
