Commit f378288e authored by Tom Lane's avatar Tom Lane

Minor copy-editing.

parent a3b0c90e
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.262 2004/04/22 04:18:37 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.263 2004/04/29 04:37:09 tgl Exp $
--> -->
<Chapter Id="runtime"> <Chapter Id="runtime">
...@@ -166,17 +166,17 @@ $ <userinput>postmaster -D /usr/local/pgsql/data</userinput> ...@@ -166,17 +166,17 @@ $ <userinput>postmaster -D /usr/local/pgsql/data</userinput>
which will leave the server running in the foreground. This must be which will leave the server running in the foreground. This must be
done while logged into the <productname>PostgreSQL</productname> user done while logged into the <productname>PostgreSQL</productname> user
account. Without <option>-D</option>, the server will try to use account. Without <option>-D</option>, the server will try to use
the data directory in the environment variable <envar>PGDATA</envar>. the data directory named by the environment variable <envar>PGDATA</envar>.
If neither of these succeed, it will fail. If that variable is not provided either, it will fail.
</para> </para>
<para> <para>
To start the <command>postmaster</command> in the Normally it is better to start the <command>postmaster</command> in the
background, use the usual shell syntax: background. For this, use the usual shell syntax:
<screen> <screen>
$ <userinput>postmaster -D /usr/local/pgsql/data &gt;logfile 2&gt;&amp;1 &amp;</userinput> $ <userinput>postmaster -D /usr/local/pgsql/data &gt;logfile 2&gt;&amp;1 &amp;</userinput>
</screen> </screen>
It is an important to store the server's <systemitem>stdout</> and It is important to store the server's <systemitem>stdout</> and
<systemitem>stderr</> output somewhere, as shown above. It will help <systemitem>stderr</> output somewhere, as shown above. It will help
for auditing purposes and to diagnose problems. (See <xref for auditing purposes and to diagnose problems. (See <xref
linkend="logfile-maintenance"> for a more thorough discussion of log linkend="logfile-maintenance"> for a more thorough discussion of log
...@@ -206,11 +206,11 @@ pg_ctl start -l logfile ...@@ -206,11 +206,11 @@ pg_ctl start -l logfile
<para> <para>
Normally, you will want to start the database server when the Normally, you will want to start the database server when the
computer boots.<indexterm><primary>booting</><secondary>starting computer boots.<indexterm><primary>booting</><secondary>starting
the server during</></> Autostart scripts are operating the server during</></> Autostart scripts are operating-system-specific.
system-specific. There are a few distributed with There are a few distributed with
<productname>PostgreSQL</productname> in the <productname>PostgreSQL</productname> in the
<filename>contrib/start-scripts</> directory. This may require root <filename>contrib/start-scripts</> directory. Installing one will require
privileges. root privileges.
</para> </para>
<para> <para>
...@@ -229,9 +229,9 @@ su -c 'pg_ctl start -D /usr/local/pgsql/data -l serverlog' postgres ...@@ -229,9 +229,9 @@ su -c 'pg_ctl start -D /usr/local/pgsql/data -l serverlog' postgres
</para> </para>
<para> <para>
Here are a few more operating system specific suggestions. (Always Here are a few more operating-system-specific suggestions. (In each
replace these with the proper installation directory and the user case be sure to use the proper installation directory and user
name.) name where we show generic values.)
<itemizedlist> <itemizedlist>
<listitem> <listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment