File: intro228.html

package info (click to toggle)
mpsql 2.1-2
  • links: PTS
  • area: non-free
  • in suites: potato
  • size: 3,528 kB
  • ctags: 4,886
  • sloc: ansic: 35,184; makefile: 3,761; sh: 44
file content (256 lines) | stat: -rw-r--r-- 4,316 bytes parent folder | download
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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Terminology</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.19"><LINK
REL="HOME"
TITLE="PostgreSQL User's Guide"
HREF="user.html"><LINK
REL="UP"
TITLE="Introduction"
HREF="intro.html"><LINK
REL="PREVIOUS"
TITLE="Resources"
HREF="intro159.html"><LINK
REL="NEXT"
TITLE="Notation"
HREF="intro259.html"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL User's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="intro159.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="intro259.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
CLASS="SECT1"
><A
NAME="AEN228"
>Terminology</A
></H1
><P
>In the following documentation,
<I
CLASS="FIRSTTERM"
>site</I
>
may be interpreted as the host machine on which 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> is installed.
Since it is possible to install more than one set of 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
>
databases on a single host, this term more precisely denotes any
particular set of installed 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> binaries and databases.&#13;</P
><P
>The 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> <I
CLASS="FIRSTTERM"
>superuser</I
>
is the user named <TT
CLASS="REPLACEABLE"
><I
>postgres</I
></TT
>
 who owns the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
>
binaries and database files.  As the database superuser, all
protection mechanisms may be bypassed and any data accessed
arbitrarily.  
In addition, the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> superuser is allowed to execute
some support programs which are generally not available to all users.
Note that the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> superuser is
<I
CLASS="EMPHASIS"
>not</I
>
the same as the Unix superuser (which will be referred to as <I
CLASS="FIRSTTERM"
>root</I
>).
The superuser should have a non-zero user identifier (<I
CLASS="FIRSTTERM"
>UID</I
>)
for security reasons.&#13;</P
><P
>The
<I
CLASS="FIRSTTERM"
>database administrator</I
>
or <SPAN
CLASS="ACRONYM"
>DBA</SPAN
>, is the person who is responsible for installing 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> with mechanisms to
enforce a security policy for a site.  The DBA can add new users by
the method described below 
and maintain a set of template databases for use by
<SPAN
CLASS="APPLICATION"
>createdb</SPAN
>.&#13;</P
><P
>The <SPAN
CLASS="APPLICATION"
>postmaster</SPAN
>
is the process that acts as a clearing-house for requests 
to the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> system.
Frontend applications connect to the <SPAN
CLASS="APPLICATION"
>postmaster</SPAN
>,
which keeps tracks of any system errors and communication between the
backend processes.  The <SPAN
CLASS="APPLICATION"
>postmaster</SPAN
>
can take several command-line arguments to tune its behavior.
However, supplying arguments is necessary only if you intend to run multiple
sites or a non-default site.&#13;</P
><P
>The <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> backend
(the actual executable program <SPAN
CLASS="APPLICATION"
>postgres</SPAN
>) may be executed
directly from the user shell by the 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> super-user 
(with the database name as an argument).  However,
doing this bypasses the shared buffer pool and lock table associated
with a postmaster/site, therefore this is not recommended in a multiuser
site.&#13;</P
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="intro159.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="user.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="intro259.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Resources</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="intro.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Notation</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>