1999-07-22 17:09:15 +02:00
|
|
|
<!--
|
2004-06-21 06:06:07 +02:00
|
|
|
$PostgreSQL: pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.50 2004/06/21 04:06:04 tgl Exp $
|
2001-12-08 04:24:40 +01:00
|
|
|
PostgreSQL documentation
|
1999-07-22 17:09:15 +02:00
|
|
|
-->
|
|
|
|
|
2000-12-26 00:15:27 +01:00
|
|
|
<refentry id="app-postmaster">
|
1999-05-26 19:25:38 +02:00
|
|
|
<refmeta>
|
2000-11-14 19:11:32 +01:00
|
|
|
<refentrytitle id="APP-POSTMASTER-TITLE"><application>postmaster</application></refentrytitle>
|
|
|
|
<manvolnum>1</manvolnum>
|
1999-05-26 19:25:38 +02:00
|
|
|
<refmiscinfo>Application</refmiscinfo>
|
|
|
|
</refmeta>
|
2000-11-14 19:11:32 +01:00
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<refnamediv>
|
2000-11-14 19:11:32 +01:00
|
|
|
<refname id="postmaster-ref">postmaster</refname>
|
2001-09-03 14:57:50 +02:00
|
|
|
<refpurpose><productname>PostgreSQL</productname> multiuser database server</refpurpose>
|
1999-05-26 19:25:38 +02:00
|
|
|
</refnamediv>
|
2000-11-14 19:11:32 +01:00
|
|
|
|
2003-08-31 19:32:24 +02:00
|
|
|
<indexterm zone="app-postmaster">
|
|
|
|
<primary>postmaster</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<refsynopsisdiv>
|
2000-11-14 19:11:32 +01:00
|
|
|
<cmdsynopsis>
|
|
|
|
<command>postmaster</command>
|
|
|
|
<arg>-A <group choice="plain"><arg>0</arg><arg>1</arg></group></arg>
|
|
|
|
<arg>-B <replaceable>nbuffers</replaceable></arg>
|
|
|
|
<arg>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
|
|
|
|
<arg>-d <replaceable>debug-level</replaceable></arg>
|
|
|
|
<arg>-D <replaceable>datadir</replaceable></arg>
|
|
|
|
<arg>-F</arg>
|
|
|
|
<arg>-h <replaceable>hostname</replaceable></arg>
|
|
|
|
<arg>-i</arg>
|
2000-12-01 00:20:51 +01:00
|
|
|
<arg>-k <replaceable>directory</replaceable></arg>
|
2000-11-14 19:11:32 +01:00
|
|
|
<arg>-l</arg>
|
|
|
|
<arg>-N <replaceable>max-connections</replaceable></arg>
|
|
|
|
<arg>-o <replaceable>extra-options</replaceable></arg>
|
|
|
|
<arg>-p <replaceable>port</replaceable></arg>
|
|
|
|
<arg>-S</arg>
|
2001-11-25 02:11:36 +01:00
|
|
|
<arg>--<replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
|
2000-11-14 19:11:32 +01:00
|
|
|
<group><arg>-n</arg><arg>-s</arg></group>
|
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> is the
|
2001-09-03 14:57:50 +02:00
|
|
|
<productname>PostgreSQL</productname> multiuser database server.
|
2000-11-14 19:11:32 +01:00
|
|
|
In order for a client application to access a database it connects
|
|
|
|
(over a network or locally) to a running
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command>. The
|
|
|
|
<command>postmaster</command> then starts a separate server
|
2000-12-26 00:15:27 +01:00
|
|
|
process (<quote><xref linkend="app-postgres"></quote>) to handle
|
2003-03-24 15:32:51 +01:00
|
|
|
the connection. The <command>postmaster</command> also
|
2000-12-26 00:15:27 +01:00
|
|
|
manages the communication among server processes.
|
2000-11-14 19:11:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
By default the <command>postmaster</command> starts in the
|
|
|
|
foreground and prints log messages to the standard error stream. In
|
|
|
|
practical applications the <command>postmaster</command>
|
2000-12-26 00:15:27 +01:00
|
|
|
should be started as a background process, perhaps at boot time.
|
2000-11-14 19:11:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
One <command>postmaster</command> always manages the data
|
2000-12-26 00:15:27 +01:00
|
|
|
from exactly one database cluster. A database cluster is a
|
|
|
|
collection of databases that is stored at a common file system
|
2003-03-24 15:32:51 +01:00
|
|
|
location. When the <command>postmaster</command> starts it needs to know the location
|
2000-12-26 00:15:27 +01:00
|
|
|
of the database cluster files (<quote>data area</quote>). This is
|
|
|
|
done with the <option>-D</option> invocation option or the
|
|
|
|
<envar>PGDATA</envar> environment variable; there is no default.
|
2003-03-24 15:32:51 +01:00
|
|
|
More than one <command>postmaster</command> process can run on a system at one time,
|
2000-12-26 00:15:27 +01:00
|
|
|
as long as they use different data areas and different
|
|
|
|
communication ports (see below). A data area is created with <xref
|
|
|
|
linkend="app-initdb">.
|
2000-11-14 19:11:32 +01:00
|
|
|
</para>
|
2002-10-12 01:03:48 +02:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1 id="app-postmaster-options">
|
|
|
|
<title>Options</title>
|
2000-11-14 19:11:32 +01:00
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> accepts the following
|
2000-11-14 19:11:32 +01:00
|
|
|
command line arguments. For a detailed discussion of the options
|
2003-03-25 17:15:44 +01:00
|
|
|
consult <xref linkend="runtime-config">. You can also save typing most of these
|
2003-01-19 01:13:31 +01:00
|
|
|
options by setting up a configuration file.
|
1999-05-26 19:25:38 +02:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-A 0|1</option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
Enables run-time assertion checks, which is a debugging aid to
|
2004-03-23 03:47:35 +01:00
|
|
|
detect programming mistakes. This option is only available if
|
|
|
|
assertions were enabled when <productname>PostgreSQL</> was
|
|
|
|
compiled. If so, the default is on.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-B <replaceable class="parameter">nbuffers</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Sets the number of shared buffers for use by the server
|
2004-03-23 03:47:35 +01:00
|
|
|
processes. The default value of this parameter is chosen
|
|
|
|
automatically by <application>initdb</application>; refer to <xref
|
|
|
|
linkend="runtime-config-resource-memory"> for more information.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2004-03-23 03:47:35 +01:00
|
|
|
Sets a named run-time parameter. The configuration parameters
|
|
|
|
supported by <productname>PostgreSQL</productname> are
|
|
|
|
described in <xref linkend="runtime-config">. Most of the
|
|
|
|
other command line options are in fact short forms of such a
|
|
|
|
parameter assignment. <option>-c</> can appear multiple times
|
|
|
|
to set multiple parameters.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-d <replaceable>debug-level</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Sets the debug level. The higher this value is set, the more
|
Commit to match discussed elog() changes. Only update is that LOG is
now just below FATAL in server_min_messages. Added more text to
highlight ordering difference between it and client_min_messages.
---------------------------------------------------------------------------
REALLYFATAL => PANIC
STOP => PANIC
New INFO level the prints to client by default
New LOG level the prints to server log by default
Cause VACUUM information to print only to the client
NOTICE => INFO where purely information messages are sent
DEBUG => LOG for purely server status messages
DEBUG removed, kept as backward compatible
DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added
DebugLvl removed in favor of new DEBUG[1-5] symbols
New server_min_messages GUC parameter with values:
DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC
New client_min_messages GUC parameter with values:
DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC
Server startup now logged with LOG instead of DEBUG
Remove debug_level GUC parameter
elog() numbers now start at 10
Add test to print error message if older elog() values are passed to elog()
Bootstrap mode now has a -d that requires an argument, like postmaster
2002-03-02 22:39:36 +01:00
|
|
|
debugging output is written to the server log. Values are from
|
2004-03-23 03:47:35 +01:00
|
|
|
1 to 5.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-D <replaceable class="parameter">datadir</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Specifies the file system location of the data directory. See
|
|
|
|
discussion above.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-F</option></term>
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Disables <function>fsync</function> calls for performance
|
2001-11-25 02:11:36 +01:00
|
|
|
improvement, at the risk of data corruption in event of a
|
2004-03-23 03:47:35 +01:00
|
|
|
system crash. Specifying this option is equivalent to
|
|
|
|
disabling the <xref linkend="guc-fsync"> configuration
|
|
|
|
parameter. Read the detailed documentation before using this!
|
2002-06-15 21:52:56 +02:00
|
|
|
</para>
|
2004-03-23 03:47:35 +01:00
|
|
|
|
2002-06-15 21:52:56 +02:00
|
|
|
<para>
|
|
|
|
<option>--fsync=true</option> has the opposite effect
|
|
|
|
of this option.
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
</para>
|
2000-11-14 19:11:32 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-h <replaceable class="parameter">hostname</replaceable></option></term>
|
2000-11-14 19:11:32 +01:00
|
|
|
<listitem>
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<para>
|
2004-03-23 02:23:48 +01:00
|
|
|
Specifies the IP host name or address on which the
|
|
|
|
<command>postmaster</command> is to listen for TCP/IP
|
2004-03-23 03:47:35 +01:00
|
|
|
connections from client applications. The value can also be a
|
|
|
|
space-separated list of addresses, or <literal>*</> to specify
|
|
|
|
listening on all available interfaces. An empty value
|
|
|
|
specifies not listening on any IP addresses, in which case
|
|
|
|
only Unix-domain sockets can be used to connect to the
|
|
|
|
<command>postmaster</command>. Defaults to listening only on
|
|
|
|
<systemitem class="systemname">localhost</systemitem>.
|
|
|
|
Specifying this option is equivalent to setting the <xref
|
2004-03-23 07:09:00 +01:00
|
|
|
linkend="guc-listen-addresses"> configuration parameter.
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-i</option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2004-03-23 02:23:48 +01:00
|
|
|
Allows remote clients to connect via TCP/IP (Internet domain)
|
|
|
|
connections. Without this option, only local connections are
|
|
|
|
accepted. This option is equivalent to setting
|
2004-03-23 03:47:35 +01:00
|
|
|
<varname>listen_addresses</> to <literal>*</> in
|
2004-03-23 02:23:48 +01:00
|
|
|
<filename>postgresql.conf</> or via <option>-h</>.
|
2002-06-15 21:52:56 +02:00
|
|
|
</para>
|
|
|
|
<para>
|
2004-03-23 02:23:48 +01:00
|
|
|
This option is deprecated since it does not allow access to the
|
2004-03-23 03:47:35 +01:00
|
|
|
full functionality of <xref linkend="guc-listen-addresses">.
|
|
|
|
It's usually better to set <varname>listen_addresses</> directly.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-k <replaceable class="parameter">directory</replaceable></option></term>
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-12-01 00:20:51 +01:00
|
|
|
Specifies the directory of the Unix-domain socket on which the
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> is to listen for
|
2000-12-01 00:20:51 +01:00
|
|
|
connections from client applications. The default is normally
|
|
|
|
<filename>/tmp</filename>, but can be changed at build time.
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
</para>
|
2000-11-14 19:11:32 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-l</option></term>
|
2000-11-14 19:11:32 +01:00
|
|
|
<listitem>
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
<para>
|
2004-03-23 03:47:35 +01:00
|
|
|
Enables secure connections using <acronym>SSL</acronym>.
|
|
|
|
<productname>PostgreSQL</productname> must have been compiled with
|
|
|
|
support for <acronym>SSL</acronym> for this option to be
|
|
|
|
available. For more information on using <acronym>SSL</acronym>,
|
|
|
|
refer to <xref linkend="ssl-tcp">.
|
UUNET is looking into offering PostgreSQL as a part of a managed web
hosting product, on both shared and dedicated machines. We currently
offer Oracle and MySQL, and it would be a nice middle-ground.
However, as shipped, PostgreSQL lacks the following features we need
that MySQL has:
1. The ability to listen only on a particular IP address. Each
hosting customer has their own IP address, on which all of their
servers (http, ftp, real media, etc.) run.
2. The ability to place the Unix-domain socket in a mode 700 directory.
This allows us to automatically create an empty database, with an
empty DBA password, for new or upgrading customers without having
to interactively set a DBA password and communicate it to (or from)
the customer. This in turn cuts down our install and upgrade times.
3. The ability to connect to the Unix-domain socket from within a
change-rooted environment. We run CGI programs chrooted to the
user's home directory, which is another reason why we need to be
able to specify where the Unix-domain socket is, instead of /tmp.
4. The ability to, if run as root, open a pid file in /var/run as
root, and then setuid to the desired user. (mysqld -u can almost
do this; I had to patch it, too).
The patch below fixes problem 1-3. I plan to address #4, also, but
haven't done so yet. These diffs are big enough that they should give
the PG development team something to think about in the meantime :-)
Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get
out what I have, which works (for the problems it tackles), now.
With these changes, we can set up and run PostgreSQL with scripts the
same way we can with apache or proftpd or mysql.
In summary, this patch makes the following enhancements:
1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT,
and command line options -k --unix-socket to the relevant programs.
2. Adds a -h option to postmaster to set the hostname or IP address to
listen on instead of the default INADDR_ANY.
3. Extends some library interfaces to support the above.
4. Fixes a few memory leaks in PQconnectdb().
The default behavior is unchanged from stock 7.0.2; if you don't use
any of these new features, they don't change the operation.
David J. MacKenzie
2000-11-13 16:18:15 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-10-08 06:28:57 +02:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-N <replaceable class="parameter">max-connections</replaceable></option></term>
|
1999-10-08 06:28:57 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Sets the maximum number of client connections that this
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> will accept. By
|
2001-11-25 02:11:36 +01:00
|
|
|
default, this value is 32, but it can be set as high as your
|
|
|
|
system will support. (Note that
|
2000-12-26 00:15:27 +01:00
|
|
|
<option>-B</option> is required to be at least twice
|
2003-03-25 17:15:44 +01:00
|
|
|
<option>-N</option>. See <xref linkend="kernel-resources"> for a discussion of
|
2003-01-19 01:13:31 +01:00
|
|
|
system resource requirements for large numbers of client
|
2004-03-23 03:47:35 +01:00
|
|
|
connections.) Specifying this option is equivalent to setting the
|
|
|
|
<xref linkend="guc-max-connections"> configuration parameter.
|
1999-10-08 06:28:57 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-o <replaceable class="parameter">extra-options</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
The command line-style options specified in <replaceable
|
2000-12-26 00:15:27 +01:00
|
|
|
class="parameter">extra-options</replaceable> are passed to
|
2003-03-24 15:32:51 +01:00
|
|
|
all server processes started by this
|
|
|
|
<command>postmaster</command>. See <xref
|
2000-12-26 00:15:27 +01:00
|
|
|
linkend="app-postgres"> for possibilities. If the option
|
|
|
|
string contains any spaces, the entire string must be quoted.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-p <replaceable class="parameter">port</replaceable></option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Specifies the TCP/IP port or local Unix domain socket file
|
2003-03-24 15:32:51 +01:00
|
|
|
extension on which the <command>postmaster</command>
|
2000-11-14 19:11:32 +01:00
|
|
|
is to listen for connections from client applications.
|
|
|
|
Defaults to the value of the <envar>PGPORT</envar> environment
|
|
|
|
variable, or if <envar>PGPORT</envar> is not set, then
|
|
|
|
defaults to the value established during compilation (normally
|
|
|
|
5432). If you specify a port other than the default port,
|
|
|
|
then all client applications must specify the same port using
|
|
|
|
either command-line options or <envar>PGPORT</envar>.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2000-11-14 19:11:32 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-S</option></term>
|
2000-11-14 19:11:32 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
Specifies that the <command>postmaster</command>
|
2000-11-14 19:11:32 +01:00
|
|
|
process should start up in silent mode. That is, it will
|
|
|
|
disassociate from the user's (controlling) terminal, start its
|
|
|
|
own process group, and redirect its standard output and
|
|
|
|
standard error to <filename>/dev/null</filename>.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Using this switch discards all logging output, which is
|
|
|
|
probably not what you want, since it makes it very difficult
|
|
|
|
to troubleshoot problems. See below for a better way to start
|
2003-03-24 15:32:51 +01:00
|
|
|
the <command>postmaster</command> in the background.
|
2000-11-14 19:11:32 +01:00
|
|
|
</para>
|
2002-06-15 21:52:56 +02:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<option>--silent-mode=false</option> has the opposite effect
|
2002-06-15 21:52:56 +02:00
|
|
|
of this option.
|
|
|
|
</para>
|
2000-11-14 19:11:32 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-11-25 02:11:36 +01:00
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>--<replaceable>name</replaceable>=<replaceable>value</replaceable></option></term>
|
2001-11-25 02:11:36 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-11-26 20:41:55 +01:00
|
|
|
Sets a named run-time parameter; a shorter form of
|
|
|
|
<option>-c</>.
|
|
|
|
</para>
|
2001-11-25 02:11:36 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
Two additional command line options are available for debugging
|
2003-03-24 15:32:51 +01:00
|
|
|
problems that cause a server process to die abnormally. The
|
|
|
|
ordinary strategy in this situation is to notify all other server
|
|
|
|
processes that they must terminate and then reinitialize the
|
|
|
|
shared memory and semaphores. This is because an errant server
|
|
|
|
process could have corrupted some shared state before terminating.
|
|
|
|
These options select alternative behaviors of the
|
|
|
|
<command>postmaster</command> in this situation.
|
|
|
|
<emphasis>Neither option is intended for use in ordinary
|
|
|
|
operation.</emphasis>
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
These special-case options are:
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-n</option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command>
|
2000-03-26 09:04:54 +02:00
|
|
|
will not reinitialize shared data structures. A knowledgeable system
|
|
|
|
programmer can then use a debugger
|
|
|
|
to examine shared memory and semaphore state.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><option>-s</option></term>
|
1999-05-26 19:25:38 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command>
|
|
|
|
will stop all other server processes by sending the signal
|
1999-05-26 19:25:38 +02:00
|
|
|
<literal>SIGSTOP</literal>,
|
|
|
|
but will not cause them to terminate. This permits system programmers
|
2003-03-24 15:32:51 +01:00
|
|
|
to collect core dumps from all server processes by hand.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Environment</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><envar>PGCLIENTENCODING</envar></term>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Default character encoding used by clients. (The clients may
|
2002-09-21 20:32:54 +02:00
|
|
|
override this individually.) This value can also be set in the
|
2002-07-28 17:22:21 +02:00
|
|
|
configuration file.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><envar>PGDATA</envar></term>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Default data direction location
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><envar>PGDATESTYLE</envar></term>
|
2002-07-28 17:22:21 +02:00
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2004-03-09 17:57:47 +01:00
|
|
|
Default value of the <xref linkend="guc-datestyle"> run-time
|
2002-07-28 17:22:21 +02:00
|
|
|
parameter. (The use of this environment variable is deprecated.)
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><envar>PGPORT</envar></term>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2002-09-21 20:32:54 +02:00
|
|
|
Default port (preferably set in the configuration file)
|
2002-07-28 17:22:21 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><envar>TZ</envar></term>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Server time zone
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Diagnostics</title>
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2003-09-12 02:12:47 +02:00
|
|
|
<para>
|
|
|
|
A failure message mentioning <literal>semget</> or <literal>shmget</>
|
|
|
|
probably indicates you need to configure your kernel to provide adequate
|
|
|
|
shared memory and semaphores. For more discussion see <xref
|
|
|
|
linkend="kernel-resources">.
|
|
|
|
</para>
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2003-09-12 02:12:47 +02:00
|
|
|
<tip>
|
|
|
|
<para>
|
2004-03-09 17:57:47 +01:00
|
|
|
You may be able to postpone reconfiguring your kernel by
|
|
|
|
decreasing <xref linkend="guc-shared-buffers"> to reduce the
|
|
|
|
shared memory consumption of <productname>PostgreSQL</>, and/or
|
|
|
|
by reducing <xref linkend="guc-max-connections"> to reduce the
|
|
|
|
semaphore consumption.
|
2003-09-12 02:12:47 +02:00
|
|
|
</para>
|
|
|
|
</tip>
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2003-09-12 02:12:47 +02:00
|
|
|
<para>
|
|
|
|
A failure message suggesting that another postmaster is already running
|
|
|
|
should be checked carefully, for example by using the command
|
2000-12-26 00:15:27 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>ps ax | grep postmaster</userinput>
|
|
|
|
</screen>
|
|
|
|
or
|
|
|
|
<screen>
|
2003-09-12 02:12:47 +02:00
|
|
|
<prompt>$</prompt> <userinput>ps -ef | grep postmaster</userinput>
|
2000-12-26 00:15:27 +01:00
|
|
|
</screen>
|
2003-09-12 02:12:47 +02:00
|
|
|
depending on your system. If you are certain that no conflicting
|
|
|
|
postmaster is running, you may remove the lock file mentioned in the
|
|
|
|
message and try again.
|
|
|
|
</para>
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2003-09-12 02:12:47 +02:00
|
|
|
<para>
|
2003-12-14 00:59:07 +01:00
|
|
|
A failure message indicating inability to bind to a port may
|
|
|
|
indicate that that port is already in use by some
|
|
|
|
non-<productname>PostgreSQL</productname> process. You may also
|
|
|
|
get this error if you terminate the <command>postmaster</command>
|
|
|
|
and immediately restart it using the same port; in this case, you
|
|
|
|
must simply wait a few seconds until the operating system closes
|
|
|
|
the port before trying again. Finally, you may get this error if
|
|
|
|
you specify a port number that your operating system considers to
|
|
|
|
be reserved. For example, many versions of Unix consider port
|
|
|
|
numbers under 1024 to be <quote>trusted</quote> and only permit
|
|
|
|
the Unix superuser to access them.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
2003-09-12 02:12:47 +02:00
|
|
|
|
2000-11-14 19:11:32 +01:00
|
|
|
</refsect1>
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2000-11-14 19:11:32 +01:00
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
If at all possible, <emphasis>do not</emphasis> use
|
|
|
|
<literal>SIGKILL</literal> to kill the
|
2003-09-18 22:30:15 +02:00
|
|
|
<command>postmaster</command>. Doing so will prevent
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> from freeing the system
|
2000-11-14 19:11:32 +01:00
|
|
|
resources (e.g., shared memory and semaphores) that it holds before
|
2003-09-18 22:30:15 +02:00
|
|
|
terminating. This may cause problems for starting a fresh
|
|
|
|
<command>postmaster</command> run.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
To terminate the <command>postmaster</command> normally,
|
2000-12-26 00:15:27 +01:00
|
|
|
the signals <literal>SIGTERM</literal>, <literal>SIGINT</literal>,
|
|
|
|
or <literal>SIGQUIT</literal> can be used. The first will wait for
|
2000-11-14 19:11:32 +01:00
|
|
|
all clients to terminate before quitting, the second will
|
|
|
|
forcefully disconnect all clients, and the third will quit
|
2001-11-25 02:11:36 +01:00
|
|
|
immediately without proper shutdown, resulting in a recovery run
|
2003-10-16 19:38:01 +02:00
|
|
|
during restart. The <literal>SIGHUP</literal> signal will
|
|
|
|
reload the server configuration files.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2000-11-14 19:11:32 +01:00
|
|
|
The utility command <xref linkend="app-pg-ctl"> can be used to
|
2003-03-24 15:32:51 +01:00
|
|
|
start and shut down the <command>postmaster</command>
|
2000-12-26 00:15:27 +01:00
|
|
|
safely and comfortably.
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
2001-11-28 21:49:10 +01:00
|
|
|
|
|
|
|
<para>
|
2002-09-21 20:32:54 +02:00
|
|
|
The <option>--</> options will not work on <systemitem
|
|
|
|
class="osname">FreeBSD</> or <systemitem class="osname">OpenBSD</>.
|
2001-11-28 21:49:10 +01:00
|
|
|
Use <option>-c</> instead. This is a bug in the affected operating
|
2002-09-21 20:32:54 +02:00
|
|
|
systems; a future release of <productname>PostgreSQL</productname>
|
|
|
|
will provide a workaround if this is not fixed.
|
2001-11-28 21:49:10 +01:00
|
|
|
</para>
|
|
|
|
|
1999-05-26 19:25:38 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
<refsect1 id="app-postmaster-examples">
|
|
|
|
<title>Examples</title>
|
2000-11-14 19:11:32 +01:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
To start <command>postmaster</command> in the background
|
2000-11-14 19:11:32 +01:00
|
|
|
using default values, type:
|
1999-05-26 19:25:38 +02:00
|
|
|
|
2000-11-14 19:11:32 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>nohup postmaster >logfile 2>&1 </dev/null &</userinput>
|
|
|
|
</screen>
|
1999-05-26 19:25:38 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
To start <command>postmaster</command> with a specific
|
2000-11-14 19:11:32 +01:00
|
|
|
port:
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>postmaster -p 1234</userinput>
|
|
|
|
</screen>
|
2003-03-24 15:32:51 +01:00
|
|
|
This command will start up <command>postmaster</command>
|
2000-11-14 19:11:32 +01:00
|
|
|
communicating through the port 1234. In order to connect to this
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>postmaster</command> using <application>psql</>, you would need to
|
2000-11-14 19:11:32 +01:00
|
|
|
run it as
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>psql -p 1234</userinput>
|
|
|
|
</screen>
|
1999-05-26 19:25:38 +02:00
|
|
|
or set the environment variable <envar>PGPORT</envar>:
|
2000-11-14 19:11:32 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>export PGPORT=1234</userinput>
|
|
|
|
<prompt>$</prompt> <userinput>psql</userinput>
|
|
|
|
</screen>
|
1999-05-27 17:49:15 +02:00
|
|
|
</para>
|
2001-11-25 02:11:36 +01:00
|
|
|
|
|
|
|
<para>
|
2002-03-22 20:20:45 +01:00
|
|
|
Named run-time parameters can be set in either of these styles:
|
2001-11-25 02:11:36 +01:00
|
|
|
<screen>
|
2004-02-03 18:34:04 +01:00
|
|
|
<prompt>$</prompt> <userinput>postmaster -c work_mem=1234</userinput>
|
|
|
|
<prompt>$</prompt> <userinput>postmaster --work-mem=1234</userinput>
|
2001-11-25 02:11:36 +01:00
|
|
|
</screen>
|
2004-02-03 18:34:04 +01:00
|
|
|
Either form overrides whatever setting might exist for <varname>work_mem</>
|
2001-11-25 02:11:36 +01:00
|
|
|
in <filename>postgresql.conf</>. Notice that underscores in parameter
|
|
|
|
names can be written as either underscore or dash on the command line.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<tip>
|
|
|
|
<para>
|
|
|
|
Except for short-term experiments,
|
|
|
|
it's probably better practice to edit the setting in
|
|
|
|
<filename>postgresql.conf</> than to rely on a command-line switch
|
|
|
|
to set a parameter.
|
|
|
|
</para>
|
|
|
|
</tip>
|
1999-05-26 19:25:38 +02:00
|
|
|
</refsect1>
|
2002-10-12 01:03:48 +02:00
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<xref linkend="app-initdb">,
|
|
|
|
<xref linkend="app-pg-ctl">
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
1999-05-26 19:25:38 +02:00
|
|
|
</refentry>
|
|
|
|
|
|
|
|
<!-- Keep this comment at the end of the file
|
|
|
|
Local variables:
|
|
|
|
mode: sgml
|
|
|
|
sgml-omittag:nil
|
|
|
|
sgml-shorttag:t
|
|
|
|
sgml-minimize-attributes:nil
|
|
|
|
sgml-always-quote-attributes:t
|
|
|
|
sgml-indent-step:1
|
|
|
|
sgml-indent-data:t
|
|
|
|
sgml-parent-document:nil
|
|
|
|
sgml-default-dtd-file:"../reference.ced"
|
|
|
|
sgml-exposed-tags:nil
|
|
|
|
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
|
|
|
sgml-local-ecat-files:nil
|
|
|
|
End:
|
|
|
|
-->
|