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
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>17.2.File Locations</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.html" title="Chapter17.Server Configuration">
<link rel="next" href="runtime-config-connection.html" title="17.3.Connections and Authentication">
<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-file-locations"></a>17.2.File Locations</h2></div></div></div>
<p> In addition to the <code class="filename">postgresql.conf</code> file
already mentioned, <span class="productname">PostgreSQL</span> uses
two other manually-edited configuration files, which control
client authentication (their use is discussed in <a href="client-authentication.html" title="Chapter20.Client Authentication">Chapter20, <i>Client Authentication</i></a>). By default, all three
configuration files are stored in the database cluster's data
directory. The options described in this section allow the
configuration files to be placed elsewhere. (Doing so can ease
administration. In particular it is often easier to ensure that
the configuration files are properly backed-up when they are
kept separate.)
</p>
<div class="variablelist"><dl>
<dt>
<a name="guc-data-directory"></a><span class="term"><code class="varname">data_directory</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Specifies the directory to use for data storage.
This option can only be set at server start.
</p></dd>
<dt>
<a name="guc-config-file"></a><span class="term"><code class="varname">config_file</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Specifies the main server configuration file
(customarily called <code class="filename">postgresql.conf</code>).
This option can only be set on the postmaster command line.
</p></dd>
<dt>
<a name="guc-hba-file"></a><span class="term"><code class="varname">hba_file</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Specifies the configuration file for host-based authentication
(customarily called <code class="filename">pg_hba.conf</code>).
This option can only be set at server start.
</p></dd>
<dt>
<a name="guc-ident-file"></a><span class="term"><code class="varname">ident_file</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Specifies the configuration file for
<span class="application">ident</span> authentication
(customarily called <code class="filename">pg_ident.conf</code>).
This option can only be set at server start.
</p></dd>
<dt>
<a name="guc-external-pid-file"></a><span class="term"><code class="varname">external_pid_file</code> (<code class="type">string</code>)</span>
</dt>
<dd><p> Specifies the name of an additional process-id (PID) file that the
<span class="application">postmaster</span> should create for use by server
administration programs.
This option can only be set at server start.
</p></dd>
</dl></div>
<p> In a default installation, none of the above options are set explicitly.
Instead, the
data directory is specified by the <code class="option">-D</code> command-line
option or the <code class="envar">PGDATA</code> environment variable, and the
configuration files are all found within the data directory.
</p>
<p> If you wish to keep the configuration files elsewhere than the
data directory, the postmaster's <code class="option">-D</code>
command-line option or <code class="envar">PGDATA</code> environment variable
must point to the directory containing the configuration files,
and the <code class="varname">data_directory</code> option must be set in
<code class="filename">postgresql.conf</code> (or on the command line) to show
where the data directory is actually located. Notice that
<code class="varname">data_directory</code> overrides <code class="option">-D</code> and
<code class="envar">PGDATA</code> for the location
of the data directory, but not for the location of the configuration
files.
</p>
<p> If you wish, you can specify the configuration file names and locations
individually using the options <code class="varname">config_file</code>,
<code class="varname">hba_file</code> and/or <code class="varname">ident_file</code>.
<code class="varname">config_file</code> can only be specified on the
<code class="command">postmaster</code> command line, but the others can be
set within the main configuration file. If all three options plus
<code class="varname">data_directory</code> are explicitly set, then it is not necessary
to specify <code class="option">-D</code> or <code class="envar">PGDATA</code>.
</p>
<p> When setting any of these options, a relative path will be interpreted
with respect to the directory in which the <code class="command">postmaster</code>
is started.
</p>
</div></body>
</html>
|
