mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03:00
Minor copy-editing.
This commit is contained in:
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.50 2007/02/16 02:10:07 alvherre Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.51 2007/07/09 01:08:09 tgl Exp $
|
||||||
PostgreSQL documentation
|
PostgreSQL documentation
|
||||||
-->
|
-->
|
||||||
|
|
||||||
@ -33,17 +33,17 @@ PostgreSQL documentation
|
|||||||
<command>postgres</command> is the
|
<command>postgres</command> is the
|
||||||
<productname>PostgreSQL</productname> database server. In order
|
<productname>PostgreSQL</productname> database server. In order
|
||||||
for a client application to access a database it connects (over a
|
for a client application to access a database it connects (over a
|
||||||
network or locally) to a running <command>postgres</command> process.
|
network or locally) to a running <command>postgres</command> instance.
|
||||||
The <command>postgres</command> instance then starts a separate server
|
The <command>postgres</command> instance then starts a separate server
|
||||||
process to handle the connection.
|
process to handle the connection.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
One <command>postgres</command> instance always manages the data from
|
One <command>postgres</command> instance always manages the data of
|
||||||
exactly one database cluster. A database cluster is a collection
|
exactly one database cluster. A database cluster is a collection
|
||||||
of databases that is stored at a common file system location (the
|
of databases that is stored at a common file system location (the
|
||||||
<quote>data area</quote>). More than one
|
<quote>data area</quote>). More than one
|
||||||
<command>postgres</command> process can run on a system at one
|
<command>postgres</command> instance can run on a system at one
|
||||||
time, so long as they use different data areas and different
|
time, so long as they use different data areas and different
|
||||||
communication ports (see below). When
|
communication ports (see below). When
|
||||||
<command>postgres</command> starts it needs to know the location
|
<command>postgres</command> starts it needs to know the location
|
||||||
@ -119,8 +119,9 @@ PostgreSQL documentation
|
|||||||
<para>
|
<para>
|
||||||
Sets the number of shared buffers for use by the server
|
Sets the number of shared buffers for use by the server
|
||||||
processes. The default value of this parameter is chosen
|
processes. The default value of this parameter is chosen
|
||||||
automatically by <application>initdb</application>; refer to <xref
|
automatically by <application>initdb</application>.
|
||||||
linkend="runtime-config-resource-memory"> for more information.
|
Specifying this option is equivalent to setting the
|
||||||
|
<xref linkend="guc-shared-buffers"> configuration parameter.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
@ -256,13 +257,9 @@ PostgreSQL documentation
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Sets the maximum number of client connections that this
|
Sets the maximum number of client connections that this
|
||||||
server will accept. By
|
server will accept. The default value of this parameter is chosen
|
||||||
default, this value is 32, but it can be set as high as your
|
automatically by <application>initdb</application>.
|
||||||
system will support. (Note that
|
Specifying this option is equivalent to setting the
|
||||||
<option>-B</option> is required to be at least twice
|
|
||||||
<option>-N</option>. See <xref linkend="kernel-resources"> for a discussion of
|
|
||||||
system resource requirements for large numbers of client
|
|
||||||
connections.) Specifying this option is equivalent to setting the
|
|
||||||
<xref linkend="guc-max-connections"> configuration parameter.
|
<xref linkend="guc-max-connections"> configuration parameter.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
@ -272,7 +269,7 @@ PostgreSQL documentation
|
|||||||
<term><option>-o <replaceable class="parameter">extra-options</replaceable></option></term>
|
<term><option>-o <replaceable class="parameter">extra-options</replaceable></option></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
The command line-style options specified in <replaceable
|
The command-line-style options specified in <replaceable
|
||||||
class="parameter">extra-options</replaceable> are passed to
|
class="parameter">extra-options</replaceable> are passed to
|
||||||
all server processes started by this
|
all server processes started by this
|
||||||
<command>postgres</command> process. If the option string contains
|
<command>postgres</command> process. If the option string contains
|
||||||
@ -354,11 +351,11 @@ PostgreSQL documentation
|
|||||||
<title>Semi-internal Options</title>
|
<title>Semi-internal Options</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
There are several other options that can be specified, used
|
The options described here are used
|
||||||
mainly for debugging purposes and in some cases to assist with
|
mainly for debugging purposes, and in some cases to assist with
|
||||||
recovery of severely damaged databases. There should be no reason
|
recovery of severely damaged databases. There should be no reason
|
||||||
to use them in a production database setup. These are listed
|
to use them in a production database setup. They are listed
|
||||||
here only for the use by <productname>PostgreSQL</productname>
|
here only for use by <productname>PostgreSQL</productname>
|
||||||
system developers. Furthermore, these options might
|
system developers. Furthermore, these options might
|
||||||
change or be removed in a future release without notice.
|
change or be removed in a future release without notice.
|
||||||
</para>
|
</para>
|
||||||
@ -500,8 +497,9 @@ PostgreSQL documentation
|
|||||||
<term><replaceable class="parameter">database</replaceable></term>
|
<term><replaceable class="parameter">database</replaceable></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Specifies the name of the database to be accessed. If it is
|
Specifies the name of the database to be accessed. This must be
|
||||||
omitted it defaults to the user name.
|
the last argument on the command line. If it is
|
||||||
|
omitted it defaults to the user name.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
@ -647,6 +645,12 @@ PostgreSQL documentation
|
|||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Notes</title>
|
<title>Notes</title>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The utility command <xref linkend="app-pg-ctl"> can be used to
|
||||||
|
start and shut down the <command>postgres</command> server
|
||||||
|
safely and comfortably.
|
||||||
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
If at all possible, <emphasis>do not</emphasis> use
|
If at all possible, <emphasis>do not</emphasis> use
|
||||||
@ -665,16 +669,14 @@ PostgreSQL documentation
|
|||||||
all clients to terminate before quitting, the second will
|
all clients to terminate before quitting, the second will
|
||||||
forcefully disconnect all clients, and the third will quit
|
forcefully disconnect all clients, and the third will quit
|
||||||
immediately without proper shutdown, resulting in a recovery run
|
immediately without proper shutdown, resulting in a recovery run
|
||||||
during restart. The <literal>SIGHUP</literal> signal will reload
|
during restart.
|
||||||
the server configuration files. It is also possible to send
|
|
||||||
<literal>SIGHUP</literal> to an individual server process, but that
|
|
||||||
is usually not sensible.
|
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The utility command <xref linkend="app-pg-ctl"> can be used to
|
The <literal>SIGHUP</literal> signal will reload
|
||||||
start and shut down the <command>postgres</command> server
|
the server configuration files. It is also possible to send
|
||||||
safely and comfortably.
|
<literal>SIGHUP</literal> to an individual server process, but that
|
||||||
|
is usually not sensible.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Reference in New Issue
Block a user