1998-09-30 07:41:54 +02:00
|
|
|
<sect1>
|
|
|
|
<title>Terminology</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
In the following documentation,
|
|
|
|
<firstterm>site</firstterm>
|
|
|
|
may be interpreted as the host machine on which
|
|
|
|
<Productname>Postgres</Productname> is installed.
|
|
|
|
Since it is possible to install more than one set of
|
|
|
|
<Productname>Postgres</Productname>
|
|
|
|
databases on a single host, this term more precisely denotes any
|
|
|
|
particular set of installed
|
|
|
|
<Productname>Postgres</Productname> binaries and databases.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The
|
1998-10-25 02:24:36 +02:00
|
|
|
<Productname>Postgres</Productname> <firstterm>superuser</firstterm>
|
1998-09-30 07:41:54 +02:00
|
|
|
is the user named <replaceable>postgres</replaceable>
|
|
|
|
who owns the <Productname>Postgres</Productname>
|
1998-10-25 02:24:36 +02:00
|
|
|
binaries and database files. As the database superuser, all
|
1998-09-30 07:41:54 +02:00
|
|
|
protection mechanisms may be bypassed and any data accessed
|
|
|
|
arbitrarily.
|
1998-10-25 02:24:36 +02:00
|
|
|
In addition, the <Productname>Postgres</Productname> superuser is allowed to execute
|
1998-09-30 07:41:54 +02:00
|
|
|
some support programs which are generally not available to all users.
|
1998-10-25 02:24:36 +02:00
|
|
|
Note that the <Productname>Postgres</Productname> superuser is
|
1998-09-30 07:41:54 +02:00
|
|
|
<emphasis>not</emphasis>
|
1998-10-25 02:24:36 +02:00
|
|
|
the same as the Unix superuser (which will be referred to as <firstterm>root</firstterm>).
|
|
|
|
The superuser should have a non-zero user identifier (<firstterm>UID</firstterm>)
|
|
|
|
for security reasons.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The
|
1998-10-25 02:24:36 +02:00
|
|
|
<firstterm>database administrator</firstterm>
|
1998-09-30 07:41:54 +02:00
|
|
|
or <acronym>DBA</acronym>, is the person who is responsible for installing
|
|
|
|
<Productname>Postgres</Productname> 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
|
|
|
|
<application>createdb</application>.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The <application>postmaster</application>
|
|
|
|
is the process that acts as a clearing-house for requests
|
|
|
|
to the <Productname>Postgres</Productname> system.
|
|
|
|
Frontend applications connect to the <application>postmaster</application>,
|
|
|
|
which keeps tracks of any system errors and communication between the
|
|
|
|
backend processes. The <application>postmaster</application>
|
|
|
|
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.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The <Productname>Postgres</Productname> backend
|
|
|
|
(the actual executable program <application>postgres</application>) may be executed
|
|
|
|
directly from the user shell by the
|
|
|
|
<Productname>Postgres</Productname> 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.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
|
|
|
</sect1>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
|
|
|
<sect1>
|
|
|
|
<title>Notation</title>
|
|
|
|
|
|
|
|
<para>
|
1998-10-27 07:15:21 +01:00
|
|
|
<quote>...</quote> or <filename>/usr/local/pgsql/</filename>
|
1998-10-25 02:24:36 +02:00
|
|
|
at the front of a file name is used to represent the
|
|
|
|
path to the <Productname>Postgres</Productname> superuser's home directory.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-10-25 02:24:36 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
In a command synopsis, brackets
|
|
|
|
<quote>[</quote> and <quote>]</quote>) indicate an optional phrase or keyword.
|
|
|
|
Anything in braces
|
|
|
|
(<quote>{</quote> and <quote>}</quote>) and containing vertical bars (<quote>|</quote>)
|
|
|
|
indicates that you must choose one.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-10-25 02:24:36 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
In examples, parentheses (<quote>(</quote> and <quote>)</quote>) are used to group boolean
|
1998-09-30 07:41:54 +02:00
|
|
|
expressions. <quote>|</quote> is the boolean operator OR.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-09-30 07:41:54 +02:00
|
|
|
|
1998-10-25 02:24:36 +02:00
|
|
|
<para>
|
|
|
|
Examples will show commands executed from various accounts and programs.
|
|
|
|
Commands executed from the root account will be preceeded with <quote>></quote>.
|
1998-10-27 07:15:21 +01:00
|
|
|
Commands executed from the <Productname>Postgres</Productname>
|
|
|
|
superuser account will be preceeded with <quote>%</quote>, while commands
|
|
|
|
executed from an unprivileged user's account will be preceeded with
|
|
|
|
<quote>$</quote>.
|
1998-10-25 02:24:36 +02:00
|
|
|
<acronym>SQL</acronym> commands will be preceeded with <quote>=></quote>
|
1998-10-27 07:15:21 +01:00
|
|
|
or will have no leading prompt, depending on the context.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-10-25 02:24:36 +02:00
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
|
|
|
At the time of writing (<Productname>Postgres</Productname> v6.4) the notation for
|
|
|
|
flagging commands is not universally consistant throughout the documentation set.
|
|
|
|
Please report problems to
|
|
|
|
<ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1998-10-25 02:24:36 +02:00
|
|
|
</note>
|
|
|
|
|
|
|
|
</sect1>
|