Commit 6f09df7f authored by Peter Eisentraut's avatar Peter Eisentraut

Minor tweaks in installation instructions, regenerate INSTALL file.

parent 37b7d5c3
This diff is collapsed.
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.29 2000/11/20 22:01:21 petere Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.30 2000/11/30 21:44:07 petere Exp $ -->
<chapter id="installation"> <chapter id="installation">
<title><![%flattext-install-include[<productname>PostgreSQL</> ]]>Installation Instructions</title> <title><![%flattext-install-include[<productname>PostgreSQL</>]]> Installation Instructions</title>
<sect1 id="install-short"> <sect1 id="install-short">
<title>Short Version</title> <title>Short Version</title>
...@@ -176,7 +176,7 @@ su - postgres ...@@ -176,7 +176,7 @@ su - postgres
<screen> <screen>
<userinput>pg_dumpall &gt; <replaceable>outputfile</></userinput> <userinput>pg_dumpall &gt; <replaceable>outputfile</></userinput>
</screen> </screen>
If you need to preserve the oids (such as when using them as If you need to preserve the OIDs (such as when using them as
foreign keys), then use the -o option when running foreign keys), then use the -o option when running
<application>pg_dumpall</>. <application>pg_dumpall</>.
</para> </para>
...@@ -206,9 +206,9 @@ su - postgres ...@@ -206,9 +206,9 @@ su - postgres
<para> <para>
On systems which have <productname>PostgreSQL</> started at boot time, there is On systems which have <productname>PostgreSQL</> started at boot time, there is
probably a start-up file that will accomplish the same thing. For probably a start-up file that will accomplish the same thing. For
example, on a Redhat Linux system one might find that example, on a Red Hat Linux system one might find that
<screen> <screen>
<userinput>/etc/rc.d/init.d/postgres.init stop</userinput> <userinput>/etc/rc.d/init.d/postgresql stop</userinput>
</screen> </screen>
works. works.
</para> </para>
...@@ -248,8 +248,7 @@ su - postgres ...@@ -248,8 +248,7 @@ su - postgres
<![%flattext-install-include[the <citetitle>Administrator's Guide</>,]]> <![%flattext-install-include[the <citetitle>Administrator's Guide</>,]]>
<![%flattext-install-ignore[<xref linkend="migration">,]]> <![%flattext-install-ignore[<xref linkend="migration">,]]>
which you are encouraged which you are encouraged
to read in any case. The <application>pg_upgrade</> utility can to read in any case.
also often be used.
</para> </para>
</sect1> </sect1>
...@@ -609,7 +608,7 @@ su - postgres ...@@ -609,7 +608,7 @@ su - postgres
<term>--with-krb5=<replaceable>DIRECTORY</></term> <term>--with-krb5=<replaceable>DIRECTORY</></term>
<listitem> <listitem>
<para> <para>
Build with suppport for Kerberos authentication. You can use Build with support for Kerberos authentication. You can use
either Kerberos version 4 or 5, but not both. The either Kerberos version 4 or 5, but not both. The
<replaceable>DIRECTORY</> argument specifies the root <replaceable>DIRECTORY</> argument specifies the root
directory of the Kerberos installation; directory of the Kerberos installation;
...@@ -855,7 +854,7 @@ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib ...@@ -855,7 +854,7 @@ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
</para> </para>
<para> <para>
On some systems it might be preferrable to set the environment On some systems it might be preferable to set the environment
variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis> variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis>
building. building.
</para> </para>
...@@ -1098,11 +1097,11 @@ gunzip -c user.ps.gz \ ...@@ -1098,11 +1097,11 @@ gunzip -c user.ps.gz \
<title>Supported Platforms</title> <title>Supported Platforms</title>
<para> <para>
At the time of release, <productname>PostgreSQL</> &version; has been verified by the <productname>PostgreSQL</> has been verified by the developer
developer community to work on the following platforms. A supported community to work on the platforms listed below. A supported
platform generally means that <productname>PostgreSQL</> builds and installs according platform generally means that <productname>PostgreSQL</> builds and
to these instructions and that the regression tests pass, except installs according to these instructions and that the regression
for minor differences. tests pass.
</para> </para>
<note> <note>
......
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/standalone-install.sgml,v 2.1 2000/07/21 00:44:13 petere Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/standalone-install.sgml,v 2.2 2000/11/30 21:44:07 petere Exp $ -->
<!-- <!--
This file helps in generating the INSTALL text file that lives in the This file helps in generating the INSTALL text file that lives in the
...@@ -15,14 +15,14 @@ this: ...@@ -15,14 +15,14 @@ this:
5. Put in place of old INSTALL file 5. Put in place of old INSTALL file
Running `make INSTALL' in the doc/src/sgml directory will do 1 through Running 'make INSTALL' in the doc/src/sgml directory will do 1 through
3 for you. 3 for you.
--> -->
<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [ <!doctype chapter PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
<!entity version "7.1"> <!entity % version SYSTEM "version.sgml">
<!entity majorversion "7.1"> %version;
<!-- <!--
The standalone version has some portions that are different from the The standalone version has some portions that are different from the
......
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