installation.sgml 64.5 KB
Newer Older
1
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.82 2002/09/21 18:32:53 petere Exp $ -->
2

3
<chapter id="installation">
4
 <title><![%standalone-include[<productname>PostgreSQL</>]]>
5
  Installation Instructions</title>
6

7 8 9 10
 <indexterm zone="installation">
  <primary>installation</primary>
 </indexterm>

11
 <sect1 id="install-short">
12 13 14
  <title>Short Version</title>

  <para>
15
<synopsis>
16 17
./configure
gmake
18
su
19 20
gmake install
adduser postgres
21 22
mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data
23 24 25 26 27
su - postgres
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data &gt;logfile 2&gt;&amp;1 &amp;
/usr/local/pgsql/bin/createdb test
/usr/local/pgsql/bin/psql test
28
</synopsis>
29
   The long version is the rest of this
30 31
   <![%standalone-include;[document.]]>
   <![%standalone-ignore;[chapter.]]>
32 33
  </para>
 </sect1>
34 35


36
 <sect1 id="install-requirements">
37
  <title>Requirements</title>
38

39 40
  <para>
   In general, a modern Unix-compatible platform should be able to run
41
   <productname>PostgreSQL</>.
42
    The platforms that had received specific testing at the
43 44 45 46 47 48
   time of release are listed in <xref linkend="supported-platforms">
   below. In the <filename>doc</> subdirectory of the distribution
   there are several platform-specific <acronym>FAQ</> documents you
   might wish to consult if you are having trouble.
  </para>

49
  <para>
50 51 52
   The following software packages are required for building
   <productname>PostgreSQL</>:

53 54 55
   <itemizedlist>
    <listitem>
     <para>
56 57 58 59
      <indexterm>
       <primary>make</primary>
      </indexterm>

60 61 62 63
      <acronym>GNU</> <application>make</> is required; other
      <application>make</> programs will <emphasis>not</> work.
      <acronym>GNU</> <application>make</> is often installed under
      the name <filename>gmake</filename>; this document will always
Peter Eisentraut's avatar
Peter Eisentraut committed
64
      refer to it by that name. (On some systems GNU make is the
65 66
      default tool with the name <filename>make</>.) To test for
      <acronym>GNU</acronym> <application>make</application> enter
67 68 69
<screen>
<userinput>gmake --version</userinput>
</screen>
Peter Eisentraut's avatar
Peter Eisentraut committed
70
      It is recommended to use version 3.76.1 or later.
71 72
     </para>
    </listitem>
73

74 75 76 77 78 79 80 81 82 83
    <listitem>
     <para>
      You need an <acronym>ISO</>/<acronym>ANSI</> C compiler. Recent
      versions of <productname>GCC</> are recommendable, but
      <productname>PostgreSQL</> is known to build with a wide variety
      of compilers from different vendors.
     </para>
    </listitem>

    <listitem>
84 85 86 87 88
     <para>
      <application>gzip</> is needed to unpack the distribution in the
      first place.  If you are reading this, you probably already got
      past that hurdle.
     </para>
89 90 91 92
    </listitem>

    <listitem>
     <para>
93 94 95 96
      <indexterm>
       <primary>readline</primary>
      </indexterm>

97 98 99 100 101 102
      The <acronym>GNU</> <productname>Readline</> library (for
      comfortable line editing and command history retrieval) will be
      used by default.  If you don't want to use it then you must
      specify the <option>--without-readline</option> option for
      <filename>configure</>.  (On <productname>NetBSD</productname>,
      the <filename>libedit</filename> library is
103 104
      <productname>readline</productname>-compatible and is used if
      <filename>libreadline</filename> is not found.)
105 106 107 108 109
     </para>
    </listitem>

    <listitem>
     <para>
110
      <indexterm>
111 112
       <primary>installation</primary>
       <secondary>on Windows</secondary>
113 114
      </indexterm>

115 116 117 118
      To build on <productname>Windows NT</> or <productname>Windows
      2000</> you need the <productname>Cygwin</> and
      <productname>cygipc</> packages. See the file
      <filename>doc/FAQ_MSWIN</> for details.
119 120
     </para>
    </listitem>
121 122
   </itemizedlist>
  </para>
123

124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148
  <para>
   The following packages are optional.  They are not required in the
   default configuration, but they are needed when certain build
   options are enabled, as explained below.

   <itemizedlist>
    <listitem>
     <para>
      To build the server programming language PL/Perl you need a full
      Perl installation, including the <filename>libperl</filename>
      library and the header files.  Since PL/Perl is a shared
      library, the <indexterm><primary>libperl</primary></indexterm>
      <filename>libperl</filename> library must be a shared library
      also on most platforms.  At the time of this writing, this is
      almost never the case in prebuilt Perl packages.
     </para>

     <para>
      If this difficulty arises in your situation, a message like this
      will appear during the build to point out this fact:
<screen>
*** Cannot build PL/Perl because libperl is not a shared library.
*** You might have to rebuild your Perl installation.  Refer to
*** the documentation for details.
</screen>
149
      (If you don't follow the on-screen output you will merely notice
150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241
      the the PL/Perl library object will not be installed.)  If you
      see this, you will have to re-build and install
      <productname>Perl</productname> manually to be able to build
      PL/Perl.  During the configuration process for
      <productname>Perl</productname>, request a shared library.
     </para>
    </listitem>

    <listitem>
     <para>
      To build the Python interface module or the PL/Python server
      programming language, you need a Python installation, including
      the header files.
     </para>

     <para>
      Since PL/Python is a shared library, the
      <indexterm><primary>libpython</primary></indexterm>
      <filename>libpython</filename> library must be a shared library
      also on most platforms.  This is not the case in a default
      Python installation.  If after building and installing you have
      a file called <filename>plpython.so</filename> (possibly a
      different extension), then everything went well.  Otherwise you
      should have seen a notice like this flying by:
<screen>
*** Cannot build PL/Python because libpython is not a shared library.
*** You might have to rebuild your Python installation.  Refer to
*** the documentation for details.
</screen>
      That means you have to rebuild (part of) your Python
      installation to supply this shared library.
     </para>

     <para>
      The catch is that the Python distribution or the Python
      maintainers do not provide any direct way to do this.  The
      closest thing we can offer you is the information in <ulink
      url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
      3.30</ulink>.  On some operating systems you don't really have
      to build a shared library, but then you will have to convince
      the PostgreSQL build system of this.  Consult the
      <filename>Makefile</filename> in the
      <filename>src/pl/plpython</filename> directory for details.
     </para>
    </listitem>

    <listitem>
     <para>
      If you want to build Tcl or Tk components (clients and the
      PL/Tcl language) you of course need a Tcl installation.
     </para>
    </listitem>

    <listitem>
     <para>
      To build the JDBC driver, you need
      <application>Ant</application> 1.5 or higher and a
      <acronym>JDK</acronym>.  <application>Ant</application> is a
      special tool for building Java-based packages.  It can be
      downloaded from the <ulink
      url="http://jakarta.apache.org/ant/index.html"><application>Ant</application>
      web site</ulink>.
     </para>

     <para>
      If you have several Java compilers installed, it depends on the
      Ant configuration which one gets used.  Precompiled
      <application>Ant</application> distributions are typically set
      up to read a file <filename>.antrc</filename> in the current
      user's home directory for configuration.  For example, to use a
      different <acronym>JDK</acronym> than the default, this may
      work:
<programlisting>
JAVA_HOME=/usr/local/sun-jdk1.3
JAVACMD=$JAVA_HOME/bin/java
</programlisting>
     </para>

     <note>
      <para>
       Do not try to build the driver by calling
       <command>ant</command> or even <command>javac</command>
       directly.  This will not work.  Run <command>gmake</command>
       normally as described below.
      </para>
     </note>
    </listitem>

    <listitem>
     <para>
      To enable Native Language Support (<acronym>NLS</acronym>), that
      is, the ability to display a program's messages in a language
242
      other than English, you need an implementation of the <application>Gettext</>
243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258
      <acronym>API</acronym>.  Some operating systems have this
      built-in (e.g., <systemitem class="osname">Linux</>, <systemitem
      class="osname">NetBSD</>, <systemitem
      class="osname">Solaris</>), for other systems you can download
      an add-on package from here: <ulink
      url="http://www.postgresql.org/~petere/gettext.html" ></ulink>.
      If you are using the <application>gettext</> implementation in
      the GNU C library then you will additionally need the
      <productname>GNU Gettext</productname> package for some utility
      programs.  For any of the other implementations you will not
      need it.
     </para>
    </listitem>

    <listitem>
     <para>
259 260
      <application>Kerberos</>, <application>OpenSSL</>, or <application>PAM</>,
      if you want to support
261 262 263 264 265 266 267 268 269 270 271 272
      authentication using these services.
     </para>
    </listitem>
   </itemizedlist>
  </para>

  <para>
   If you are build from a CVS tree instead of using a released source
   package, or if you want to do development, you also need the
   following packages:

   <itemizedlist>
273 274
    <listitem>
     <para>
275
      <indexterm>
276 277 278 279 280 281 282
       <primary>flex</primary>
      </indexterm>
      <indexterm>
       <primary>bison</primary>
      </indexterm>
      <indexterm>
       <primary>yacc</primary>
283 284
      </indexterm>

285 286 287 288 289 290 291 292
      <acronym>GNU</> <application>Flex</> and <application>Bison</>
      are needed to build a CVS checkout or if you changed the actual
      scanner and parser definition files. If you need them, be sure
      to get <application>Flex</> 2.5.4 or later and
      <application>Bison</> 1.28 or later. Other <application>yacc</>
      programs can sometimes be used, but doing so requires extra
      effort and is not recommended. Other <application>lex</>
      programs will definitely not work.
293 294
     </para>
    </listitem>
295 296
   </itemizedlist>
  </para>
297

298 299 300
  <para>
   If you need to get a <acronym>GNU</acronym> package, you can find
   it at your local <acronym>GNU</acronym> mirror site (see <ulink
301
   url="http://www.gnu.org/order/ftp.html"></>
302
   for a list) or at <ulink
303
   url="ftp://ftp.gnu.org/gnu/"></ulink>.
304 305 306 307
  </para>

  <para>
   Also check that you have sufficient disk space. You will need about
308 309 310 311 312 313 314
   65 MB for the source tree during compilation and about 15 MB for
   the installation directory. An empty database cluster takes about
   25 MB, databases take about five times the amount of space that a
   flat text file with the same data would take. If you are going to
   run the regression tests you will temporarily need up to an extra
   90 MB. Use the <command>df</command> command to check for disk
   space.
315
  </para>
316
 </sect1>
317

318
<![%standalone-ignore;[
319
 <sect1 id="install-getsource">
320
  <title>Getting The Source</title>
321

322
  <para>
323 324
   The <productname>PostgreSQL</> &version; sources can be obtained by
   anonymous FTP from <ulink
325
   url="ftp://ftp.postgresql.org/pub/postgresql-&version;.tar.gz"></ulink>.
Peter Eisentraut's avatar
Peter Eisentraut committed
326
   Use a mirror if possible. After you have obtained the file, unpack it:
327 328 329 330 331
<screen>
<userinput>gunzip postgresql-&version;.tar.gz</userinput>
<userinput>tar xf postgresql-&version;.tar</userinput>
</screen>
   This will create a directory
Peter Eisentraut's avatar
Peter Eisentraut committed
332 333 334
   <filename>postgresql-&version;</filename> under the current directory
   with the <productname>PostgreSQL</> sources.
   Change into that directory for the rest
335 336 337 338 339 340 341 342
   of the installation procedure.
  </para>
 </sect1>
]]>

 <sect1 id="install-upgrading">
  <title>If You Are Upgrading</title>

343 344 345 346
  <indexterm zone="install-upgrading">
   <primary>upgrading</primary>
  </indexterm>

347 348
  <para>
   The internal data storage format changes with new releases of
349 350
   <productname>PostgreSQL</>. Therefore, if you are upgrading an
   existing installation that does not have a version number
351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371
   <quote>&majorversion;.x</quote>, you must back up and restore your
   data as shown here. These instructions assume that your existing
   installation is under the <filename>/usr/local/pgsql</> directory,
   and that the data area is in <filename>/usr/local/pgsql/data</>.
   Substitute your paths appropriately.
  </para>

  <procedure>
   <step>
    <para>
     Make sure that your database is not updated during or after the
     backup. This does not affect the integrity of the backup, but the
     changed data would of course not be included. If necessary, edit
     the permissions in the file
     <filename>/usr/local/pgsql/data/pg_hba.conf</> (or equivalent) to
     disallow access from everyone except you.
    </para>
   </step>

   <step>
    <para>
372 373 374 375
     <indexterm>
      <primary>pg_dumpall</primary>
     </indexterm>

376 377 378 379
     To dump your database installation, type:
<screen>
<userinput>pg_dumpall &gt; <replaceable>outputfile</></userinput>
</screen>
380
     If you need to preserve OIDs (such as when using them as
381
     foreign keys), then use the <option>-o</option> option when running
382 383 384 385 386
     <command>pg_dumpall</>.
    </para>

    <para>
     <command>pg_dumpall</command> does not
387
     save large objects.  Check
388 389
     <![%standalone-include[the <citetitle>Administrator's Guide</>]]>
     <![%standalone-ignore[<xref linkend="backup-dump-caveats">]]>
390
     if you need to do this.
391 392 393
    </para>

    <para>
394
     Make sure that you use the <command>pg_dumpall</> command
395
     from the version you are currently running. &version;'s
396
     <command>pg_dumpall</> should not be used on older databases.
397 398
    </para>
   </step>
399

400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415
   <step>
    <para>
     If you are installing the new version at the same location as the
     old one then shut down the old server, at the latest before you
     install the new files:
<screen>
<userinput>kill -INT `cat /usr/local/pgsql/data/postmaster.pid`</>
</screen>
     Versions prior to 7.0 do not have this
     <filename>postmaster.pid</> file. If you are using such a version
     you must find out the process id of the server yourself, for
     example by typing <userinput>ps ax | grep postmaster</>, and
     supply it to the <command>kill</> command.
    </para>

    <para>
416
     On systems that have <productname>PostgreSQL</> started at boot time, there is
417
     probably a start-up file that will accomplish the same thing. For
418
     example, on a <systemitem class="osname">Red Hat Linux</> system one might find that
419
<screen>
420
<userinput>/etc/rc.d/init.d/postgresql stop</userinput>
421
</screen>
422
     works.  Another possibility is <userinput>pg_ctl stop</>.
423 424 425 426 427 428 429
    </para>
   </step>

   <step>
    <para>
     If you are installing in the same place as the old version then
     it is also a good idea to move the old installation out of the
430 431
     way, in case you have trouble and need to revert to it.
     Use a command like this:
432 433 434 435 436 437 438 439 440 441 442 443 444
<screen>
<userinput>mv /usr/local/pgsql /usr/local/pgsql.old</>
</screen>
    </para>
   </step>
  </procedure>

  <para>
   After you have installed <productname>PostgreSQL</> &version;, create a new database
   directory and start the new server. Remember that you must execute
   these commands while logged in to the special database user account
   (which you already have if you are upgrading).
<programlisting>
Peter Eisentraut's avatar
Peter Eisentraut committed
445 446
<userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</>
<userinput>/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data</>
447 448 449 450 451 452 453
</programlisting>
   Finally, restore your data with
<screen>
<userinput>/usr/local/pgsql/bin/psql -d template1 -f <replaceable>outputfile</></userinput>
</screen>
   using the <emphasis>new</> <application>psql</>.
  </para>
454 455

  <para>
456
   You can also install the new version in parallel with the old one
Peter Eisentraut's avatar
typos  
Peter Eisentraut committed
457
   to decrease the downtime. These topics are discussed at length in
458 459
   <![%standalone-include[the <citetitle>Administrator's Guide</>,]]>
   <![%standalone-ignore[<xref linkend="migration">,]]>
460
   which you are encouraged
461
   to read in any case.
462
  </para>
463 464 465
 </sect1>


466
 <sect1 id="install-procedure">
467 468 469 470 471 472
  <title>Installation Procedure</title>

  <procedure>

  <step id="configure">
   <title>Configuration</>
473 474 475 476 477

   <indexterm zone="configure">
    <primary>configure</primary>
   </indexterm>

478
   <para>
Peter Eisentraut's avatar
typos  
Peter Eisentraut committed
479
    The first step of the installation procedure is to configure the
480 481
    source tree for your system and choose the options you would like.
    This is done by running the <filename>configure</> script. For a
482
    default installation simply enter
483 484 485 486 487
<screen>
<userinput>./configure</userinput>
</screen>
    This script will run a number of tests to guess values for various
    system dependent variables and detect some quirks of your
488 489 490 491
    operating system, and finally will create several files in the
    build tree to record what it found.  (You can also run
    <filename>configure</filename> in a directory outside the source
    tree if you want to keep the build directory separate.)
492 493 494 495
   </para>

   <para>
    The default configuration will build the server and utilities, as
496
    well as all client applications and interfaces that require only a
497 498 499 500 501
    C compiler. All files will be installed under
    <filename>/usr/local/pgsql</> by default.
   </para>

   <para>
502
    You can customize the build and installation process by supplying one
503 504 505 506 507
    or more of the following command line options to
    <filename>configure</filename>:

     <variablelist>
      <varlistentry>
508
       <term><option>--prefix=<replaceable>PREFIX</></option></term>
509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525
       <listitem>
        <para>
         Install all files under the directory <replaceable>PREFIX</>
         instead of <filename>/usr/local/pgsql</filename>. The actual
         files will be installed into various subdirectories; no files
         will ever be installed directly into the
         <replaceable>PREFIX</> directory.
        </para>

        <para>
         If you have special needs, you can also customize the
         individual subdirectories with the following options.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
526
       <term><option>--exec-prefix=<replaceable>EXEC-PREFIX</></option></term>
527 528 529 530 531 532 533
       <listitem>
        <para>
         You can install architecture-dependent files under a
         different prefix, <replaceable>EXEC-PREFIX</>, than what
         <replaceable>PREFIX</> was set to. This can be useful to
         share architecture-independent files between hosts. If you
         omit this, then <replaceable>EXEC-PREFIX</> is set equal to
Peter Eisentraut's avatar
Peter Eisentraut committed
534
         <replaceable>PREFIX</> and both architecture-dependent and
535 536 537 538 539 540 541
         independent files will be installed under the same tree,
         which is probably what you want.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
542
       <term><option>--bindir=<replaceable>DIRECTORY</></option></term>
543 544 545 546 547 548 549 550 551 552
       <listitem>
        <para>
         Specifies the directory for executable programs. The default
         is <filename><replaceable>EXEC-PREFIX</>/bin</>, which
         normally means <filename>/usr/local/pgsql/bin</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
553
       <term><option>--datadir=<replaceable>DIRECTORY</></option></term>
554 555 556 557 558 559 560 561 562 563 564
       <listitem>
        <para>
         Sets the directory for read-only data files used by the
         installed programs. The default is
         <filename><replaceable>PREFIX</>/share</>. Note that this has
         nothing to do with where your database files will be placed.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
565
       <term><option>--sysconfdir=<replaceable>DIRECTORY</></option></term>
566 567 568 569 570 571 572 573 574
       <listitem>
        <para>
         The directory for various configuration files,
         <filename><replaceable>PREFIX</>/etc</> by default.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
575
       <term><option>--libdir=<replaceable>DIRECTORY</></option></term>
576 577 578 579 580 581 582 583 584 585
       <listitem>
        <para>
         The location to install libraries and dynamically loadable
         modules. The default is
         <filename><replaceable>EXEC-PREFIX</>/lib</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
586
       <term><option>--includedir=<replaceable>DIRECTORY</></option></term>
587 588 589 590 591 592 593 594 595
       <listitem>
        <para>
         The directory for installing C and C++ header files. The
         default is <filename><replaceable>PREFIX</>/include</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
596
       <term><option>--docdir=<replaceable>DIRECTORY</></option></term>
597 598 599 600 601 602 603 604 605 606
       <listitem>
        <para>
         Documentation files, except <quote>man</> pages, will be
         installed into this directory. The default is
         <filename><replaceable>PREFIX</>/doc</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
607
       <term><option>--mandir=<replaceable>DIRECTORY</></option></term>
608 609 610 611 612
       <listitem>
        <para>
         The man pages that come with <productname>PostgreSQL</> will be installed under
         this directory, in their respective
         <filename>man<replaceable>x</></> subdirectories.
613
         The default is <filename><replaceable>PREFIX</>/man</>.
614 615 616
        </para>
       </listitem>
      </varlistentry>
617 618 619 620
     </variablelist>

     <note>
      <para>
621 622
       Care has been taken to make it possible to install
	<productname>PostgreSQL</> 
623 624 625 626 627 628 629
       into shared installation locations (such as
       <filename>/usr/local/include</filename>) without interfering
       with the namespace of the rest of the system.  First, the
       string <quote><literal>/postgresql</literal></quote> is
       automatically appended to <varname>datadir</varname>,
       <varname>sysconfdir</varname>, and <varname>docdir</varname>,
       unless the fully expanded directory name already contains the
630
       string <quote><literal>postgres</></quote> or <quote><literal>pgsql</></quote>.  For
631 632 633 634
       example, if you choose <filename>/usr/local</filename> as
       prefix, the documentation will be installed in
       <filename>/usr/local/doc/postgresql</filename>, but if the
       prefix is <filename>/opt/postgres</filename>, then it will be
635
       in <filename>/opt/postgres/doc</filename>.  The public C header files of the
636 637 638 639
       client interfaces are installed into
       <varname>includedir</varname> and are namespace-clean.  The
       internal header files and the server header files are installed
       into private directories under
640
       <varname>includedir</varname>.
641
       See the <citetitle>Programmer's Guide</citetitle> for
Peter Eisentraut's avatar
Peter Eisentraut committed
642
       information about how to get at the header files for each interface.
643 644
       Finally, a private subdirectory will also be created, if appropriate,
       under <varname>libdir</varname> for dynamically loadable modules.       
645 646 647
      </para>
     </note>
    </para>
648

649 650
    <para>
     <variablelist>
651
      <varlistentry>
652
       <term><option>--with-includes=<replaceable>DIRECTORIES</></option></term>
653 654 655 656 657
       <listitem>
        <para>
         <replaceable>DIRECTORIES</> is a colon-separated list of
         directories that will be added to the list the compiler
         searches for header files. If you have optional packages
658 659 660
         (such as GNU <application>Readline</>) installed in a non-standard
	 location,
         you have to use this option and probably also the corresponding
661 662 663 664 665 666 667 668 669
         <option>--with-libraries</> option.
        </para>
        <para>
         Example: <literal>--with-includes=/opt/gnu/include:/usr/sup/include</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
670
       <term><option>--with-libraries=<replaceable>DIRECTORIES</></option></term>
671 672 673 674 675 676 677 678 679 680 681 682 683 684 685
       <listitem>
        <para>
         <replaceable>DIRECTORIES</> is a colon-separated list of
         directories to search for libraries. You will probably have
         to use this option (and the corresponding
         <option>--with-includes</> option) if you have packages
         installed in non-standard locations.
        </para>
        <para>
         Example: <literal>--with-libraries=/opt/gnu/lib:/usr/sup/lib</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
686
       <term><option>--enable-recode</option></term>
687 688
       <listitem>
        <para>
689
         Enables single-byte character set recode support. See
690 691 692 693 694
         <![%standalone-include[the <citetitle>Administrator's
         Guide</citetitle>]]> <![%standalone-ignore[<xref
         linkend="recode">]]> about this feature.  Note that a more
         general form of character set conversion is supported in the
         default configuration; this feature is obsolete.
Peter Eisentraut's avatar
Peter Eisentraut committed
695
        </para>
696 697 698
       </listitem>
      </varlistentry>

699
      <varlistentry>
700
       <term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term>
701 702
       <listitem>
        <para>
703 704 705 706 707 708 709 710 711 712
         Enables Native Language Support (<acronym>NLS</acronym>),
         that is, the ability to display a program's messages in a
         language other than English.
         <replaceable>LANGUAGES</replaceable> is a space separated
         list of codes of the languages that you want supported, for
         example <literal>--enable-nls='de fr'</>.  (The intersection
         between your list and the set of actually provided
         translations will be computed automatically.)  If you do not
         specify a list, then all available translations are
         installed.
713 714 715 716
        </para>

        <para>
         To use this option, you will need an implementation of the
717
         <application>gettext</> API; see above.
718 719 720 721
        </para>
       </listitem>
      </varlistentry>

722
      <varlistentry>
723
       <term><option>--with-pgport=<replaceable>NUMBER</></option></term>
724 725 726 727 728 729
       <listitem>
        <para>
         Set <replaceable>NUMBER</> as the default port number for
         server and clients. The default is 5432. The port can always
         be changed later on, but if you specify it here then both
         server and clients will have the same default compiled in,
730 731 732
         which can be very convenient.  Usually the only good reason
	 to select a non-default value is if you intend to run multiple
	 <productname>PostgreSQL</> servers on the same machine.
733 734 735 736 737
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
738
       <term><option>--with-perl</option></term>
739 740
       <listitem>
        <para>
741
         Build the PL/Perl server-side language.
742 743 744 745 746
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
747
       <term><option>--with-python</option></term>
748 749
       <listitem>
        <para>
750 751 752
         Build the Python interface module and the PL/Python
         server-side language. You need to have root access to be able
         to install the Python module at its default place
753 754 755 756 757 758 759 760 761 762
         (<filename>/usr/lib/python<replaceable>x</>.<replaceable>y</></>).
         To be able to use this option, you must have Python installed
         and your system needs to support shared libraries. If you
         instead want to build a new complete interpreter binary, you
         will have to do it manually.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
763
       <term><option>--with-tcl</option></term>
764 765
       <listitem>
        <para>
766 767
         Builds components that require Tcl/Tk, which are
         <application>libpgtcl</>, <application>pgtclsh</>,
768
         <application>pgtksh</application>,
769
         and <application>PL/Tcl</>.  But see below about
770
         <option>--without-tk</>.
771 772 773 774 775
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
776
       <term><option>--without-tk</option></term>
777 778
       <listitem>
        <para>
779
         If you specify <option>--with-tcl</> and this option, then
780 781
         the program that requires <productname>Tk</>
         (<application>pgtksh</>) will be
782
         excluded.
783 784 785 786 787
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
788 789
       <term><option>--with-tclconfig=<replaceable>DIRECTORY</replaceable></option></term>
       <term><option>--with-tkconfig=<replaceable>DIRECTORY</replaceable></option></term>
790 791 792
       <listitem>
        <para>
         Tcl/Tk installs the files <filename>tclConfig.sh</filename> and
793 794
         <filename>tkConfig.sh</filename>, which contain
         configuration information needed to build modules
795
         interfacing to Tcl or Tk. These files are normally found
796
         automatically at their well-known locations, but if you want to
797
         use a different version of Tcl or Tk you can specify the
798
         directory in which to find them.
799 800 801 802
        </para>
       </listitem>
      </varlistentry>

803 804 805 806 807
      <varlistentry>
       <term><option>--with-java</option></term>
       <listitem>
        <para>
         Build the <acronym>JDBC</acronym> driver and associated Java
808
         packages.
809 810 811 812
        </para>
       </listitem>
      </varlistentry>

813
      <varlistentry>
Peter Eisentraut's avatar
Peter Eisentraut committed
814 815
       <term><option>--with-krb4<optional>=<replaceable>DIRECTORY</></></option></term>
       <term><option>--with-krb5<optional>=<replaceable>DIRECTORY</></></option></term>
816 817
       <listitem>
        <para>
818
         Build with support for Kerberos authentication. You can use
819 820 821 822
         either Kerberos version 4 or 5, but not both. The
         <replaceable>DIRECTORY</> argument specifies the root
         directory of the Kerberos installation;
         <filename>/usr/athena</> is assumed as default. If the
823
         relevant header files and libraries are not under a common
824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840
         parent directory, then you must use the
         <option>--with-includes</> and <option>--with-libraries</>
         options in addition to this option. If, on the other hand,
         the required files are in a location that is searched by
         default (e.g., <filename>/usr/lib</>), then you can leave off
         the argument.
        </para>

        <para>
         <filename>configure</> will check for the required header
         files and libraries to make sure that your Kerberos
         installation is sufficient before proceeding.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
841
       <term><option>--with-krb-srvnam=<replaceable>NAME</></option></term>
842 843 844
       <listitem>
        <para>
         The name of the Kerberos service principal.
845
         <literal>postgres</literal> is the default. There's probably no
846 847 848 849 850
         reason to change this.
        </para>
       </listitem>
      </varlistentry>

851
      <varlistentry>
852 853 854 855 856
       <indexterm>
        <primary>OpenSSL</primary>
        <seealso>SSL</seealso>
       </indexterm>

Peter Eisentraut's avatar
Peter Eisentraut committed
857
       <term><option>--with-openssl<optional>=<replaceable>DIRECTORY</></></option></term>
858 859
       <listitem>
        <para>
860 861
         Build with support for <acronym>SSL</> (encrypted) connections. 
         This requires the <productname>OpenSSL</> package to be installed.
862
         The <replaceable>DIRECTORY</> argument specifies the
863 864
         root directory of the <productname>OpenSSL</> installation; the
         default is <filename>/usr/local/ssl</>.
865 866 867 868
        </para>

        <para>
         <filename>configure</> will check for the required header
869
         files and libraries to make sure that your <productname>OpenSSL</>
870 871 872 873 874
         installation is sufficient before proceeding.
        </para>
       </listitem>
      </varlistentry>

Peter Eisentraut's avatar
Peter Eisentraut committed
875
      <varlistentry>
876
       <term><option>--with-pam</option></term>
Peter Eisentraut's avatar
Peter Eisentraut committed
877 878
       <listitem>
        <para>
879 880
	 Build with <acronym>PAM</> (Pluggable Authentication Modules)
	 support.
Peter Eisentraut's avatar
Peter Eisentraut committed
881 882 883 884
        </para>
       </listitem>
      </varlistentry>

885 886 887 888
      <varlistentry>
       <term><option>--without-readline</option></term>
       <listitem>
        <para>
889
         Prevents the use of the <application>Readline</> library.  This disables
890 891 892 893 894 895 896 897 898 899
         command-line editing and history in
         <application>psql</application>, so it is not recommended.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
       <term><option>--without-zlib</option></term>
       <listitem>
        <para>
900
         Prevents the use of the <application>Zlib</> library.  This disables
901 902 903 904 905 906 907
         compression support in <application>pg_dump</application>.
         This option is only intended for those rare systems where this
         library is not available.
        </para>
       </listitem>
      </varlistentry>

908
      <varlistentry>
909
       <term><option>--enable-debug</option></term>
910 911 912 913
       <listitem>
        <para>
         Compiles all programs and libraries with debugging symbols.
         This means that you can run the programs through a debugger
Tom Lane's avatar
Tom Lane committed
914
         to analyze problems. This enlarges the size of the installed
915
	 executables considerably, and on non-GCC compilers it usually
Tom Lane's avatar
Tom Lane committed
916 917 918
	 also disables compiler optimization, causing slowdowns. However,
	 having the symbols available is extremely helpful for dealing
	 with any problems that may arise.  Currently, this option is
919
	 recommended for production installations only if you use GCC.
920
	 But you should always have it on if you are doing development work
921
	 or running a beta version.
Tom Lane's avatar
Tom Lane committed
922 923 924 925 926
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
927
       <term><option>--enable-cassert</option></term>
Tom Lane's avatar
Tom Lane committed
928 929 930 931 932 933 934 935
       <listitem>
        <para>
	 Enables <firstterm>assertion</> checks in the server, which test for
	 many <quote>can't happen</> conditions.  This is invaluable for
	 code development purposes, but the tests slow things down a little.
	 Also, having the tests turned on won't necessarily enhance the
	 stability of your server!  The assertion checks are not categorized
	 for severity, and so what might be a relatively harmless bug will
Peter Eisentraut's avatar
Peter Eisentraut committed
936
	 still lead to server restarts if it triggers an assertion
Tom Lane's avatar
Tom Lane committed
937 938 939
	 failure.  Currently, this option is not recommended for
         production use, but you should have it on for development work
	 or when running a beta version.
940 941 942
        </para>
       </listitem>
      </varlistentry>
943 944 945 946 947 948 949 950 951 952 953 954 955 956 957

      <varlistentry>
       <term><option>--enable-depend</option></term>
       <listitem>
        <para>
	 Enables automatic dependency tracking.  With this option, the
	 makefiles are set up so that all affected object files will
	 be rebuilt when any header file is changed.  This is useful
	 if you are doing development work, but is just wasted overhead
	 if you intend only to compile once and install.  At present,
	 this option will work only if you use GCC.
        </para>
       </listitem>
      </varlistentry>

958
     </variablelist>
959
    </para>
960

961 962 963 964 965 966 967 968 969 970 971 972 973
    <para>
     If you prefer a C compiler different from the one
     <filename>configure</filename> picks then you can set the
     environment variable <envar>CC</> to the program of your choice.
     By default, <filename>configure</filename> will pick
     <filename>gcc</filename> unless this is inappropriate for the
     platform.  Similarly, you can override the default compiler flags
     with the <envar>CFLAGS</envar> variable.
    </para>

    <para>
     You can specify environment variables on the
     <filename>configure</filename> command line, for example:
974
<screen>
975
<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'</>
976
</screen>
977 978
    </para>
   </step>
979 980 981 982 983 984 985 986 987 988

  <step>
   <title>Build</title>

   <para>
    To start the build, type
<screen>
<userinput>gmake</userinput>
</screen>
    (Remember to use <acronym>GNU</> <application>make</>.) The build
989 990
    may take anywhere from 5 minutes to half an hour depending on your
    hardware. The last line displayed should be
991 992 993 994 995 996 997 998 999
<screen>
All of PostgreSQL is successfully made. Ready to install.
</screen>
   </para>
  </step>

  <step>
   <title>Regression Tests</title>

1000 1001 1002 1003
   <indexterm>
    <primary>regression test</primary>
   </indexterm>

1004 1005 1006
   <para>
    If you want to test the newly built server before you install it,
    you can run the regression tests at this point. The regression
1007 1008 1009
    tests are a test suite to verify that <productname>PostgreSQL</>
    runs on your machine in the way the developers expected it
    to. Type
1010
<screen>
1011
<userinput>gmake check</userinput>
1012
</screen>
1013
    (This won't work as root; do it as an unprivileged user.)
1014
    It is possible that some tests fail, due to differences in error
1015
    message wording or floating point results.
1016
    <![%standalone-include[The file
1017 1018
    <filename>src/test/regress/README</> and the
    <citetitle>Administrator's Guide</citetitle> contain]]>
1019
    <![%standalone-ignore[<xref linkend="regress"> contains]]>
1020 1021
    detailed information about interpreting the test results. You can
    repeat this test at any later time by issuing the same command.
1022 1023 1024 1025 1026 1027 1028 1029 1030
   </para>
  </step>

  <step id="install">
   <title>Installing The Files</title>

   <note>
    <para>
     If you are upgrading an existing system and are going to install
1031
     the new files over the old ones, then you should have backed up
1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049
     your data and shut down the old server by now, as explained in
     <xref linkend="install-upgrading"> above.
    </para>
   </note>

   <para>
    To install <productname>PostgreSQL</> enter
<screen>
<userinput>gmake install</userinput>
</screen>
    This will install files into the directories that were specified
    in <xref linkend="configure">. Make sure that you have appropriate
    permissions to write into that area. Normally you need to do this
    step as root. Alternatively, you could create the target
    directories in advance and arrange for appropriate permissions to
    be granted.
   </para>

1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062
   <para>
    You can use <literal>gmake install-strip</literal> instead of
    <literal>gmake install</literal> to strip the executable files and
    libraries as they are installed.  This will save some space.  If
    you built with debugging support, stripping will effectively
    remove the debugging support, so it should only be done if
    debugging is no longer needed.  <literal>install-strip</literal>
    tries to do a reasonable job saving space, but it does not have
    perfect knowledge of how to strip every unneeded byte from an
    executable file, so if you want to save all the disk space you
    possibly can, you will have to do manual work.
   </para>

1063
   <para>
1064
    If you built the Python interfaces and you were not the
1065 1066 1067 1068 1069 1070
    root user when you executed the above command then that part of
    the installation probably failed. In that case you should become
    the root user and then do
<screen>
<userinput>gmake -C src/interfaces/python install</userinput>
</screen>
1071 1072 1073 1074
    If you do not have superuser access you are on your own: 
    you can still take the required files and place them in 
    other directories where Python can find them, but how to 
    do that is left as an exercise.
1075 1076
   </para>

1077
   <para>
1078
    The standard installation provides only the header files needed for client
1079
    application development.  If you plan to do any server-side program
1080
    development (such as custom functions or data types written in C),
1081 1082 1083 1084 1085
    then you may want to install the entire <productname>PostgreSQL</>
    include tree into your target include directory.  To do that, enter
<screen>
<userinput>gmake install-all-headers</userinput>
</screen>
Peter Eisentraut's avatar
Peter Eisentraut committed
1086
    This adds a megabyte or two to the installation footprint, and is only
1087 1088 1089 1090 1091
    useful if you don't plan to keep the whole source tree around for
    reference.  (If you do, you can just use the source's include
    directory when building server-side software.)
   </para>

1092
   <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1093
    <title>Client-only installation:</title>
1094 1095
    <para>
     If you want to install only the client applications and
1096
     interface libraries, then you can use these commands:
1097 1098
<screen>
<userinput>gmake -C src/bin install</>
1099
<userinput>gmake -C src/include install</>
1100 1101 1102 1103 1104
<userinput>gmake -C src/interfaces install</>
<userinput>gmake -C doc install</>
</screen>
    </para>
   </formalpara>
1105 1106
  </step>
  </procedure>
1107

1108 1109
  <formalpara>
   <title>Uninstall:</title>
1110 1111
   <para>
    To undo the installation use the command <command>gmake
1112
    uninstall</>. However, this will not remove any created directories.
1113
   </para>
1114
  </formalpara>
1115

1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129
  <formalpara>
   <title>Cleaning:</title>

   <para>
    After the installation you can make room by removing the built
    files from the source tree with the command <command>gmake
    clean</>. This will preserve the files made by the configure
    program, so that you can rebuild everything with <command>gmake</>
    later on. To reset the source tree to the state in which it was
    distributed, use <command>gmake distclean</>. If you are going to
    build for several platforms from the same source tree you must do
    this and re-configure for each build.
   </para>
  </formalpara>
1130

1131
  <para>
1132 1133 1134 1135 1136
   If you perform a build and then discover that your configure
   options were wrong, or if you change anything that configure
   investigates (for example, software upgrades), then it's a good
   idea to do <command>gmake distclean</> before reconfiguring and
   rebuilding.  Without this, your changes in configuration choices
1137 1138
   may not propagate everywhere they need to.
  </para>
1139 1140
 </sect1>

1141
 <sect1 id="install-post">
1142 1143 1144 1145
  <title>Post-Installation Setup</title>

  <sect2>
   <title>Shared Libraries</title>
1146 1147 1148 1149 1150

   <indexterm>
    <primary>shared libraries</primary>
   </indexterm>

1151
   <para>
1152
    On some systems that have shared libraries (which most systems do)
1153
    you need to tell your system how to find the newly installed
1154
    shared libraries.  The systems on which this is
1155 1156 1157 1158 1159 1160 1161 1162
    <emphasis>not</emphasis> necessary include <systemitem
    class="osname">BSD/OS</>, <systemitem class="osname">FreeBSD</>,
    <systemitem class="osname">HP-UX</>, <systemitem
    class="osname">IRIX</>, <systemitem class="osname">Linux</>,
    <systemitem class="osname">NetBSD</>, <systemitem
    class="osname">OpenBSD</>, <systemitem class="osname">Tru64
    UNIX</> (formerly <systemitem class="osname">Digital UNIX</>), and
    <systemitem class="osname">Solaris</>.
1163 1164 1165 1166 1167 1168
   </para>

   <para>
    The method to set the shared library search path varies between
    platforms, but the most widely usable method is to set the
    environment variable <envar>LD_LIBRARY_PATH</> like so: In Bourne
1169
    shells (<command>sh</>, <command>ksh</>, <command>bash</>, <command>zsh</>)
1170 1171 1172 1173
<programlisting>
LD_LIBRARY_PATH=/usr/local/pgsql/lib
export LD_LIBRARY_PATH
</programlisting>
1174
    or in <command>csh</> or <command>tcsh</>
1175 1176 1177 1178 1179
<programlisting>
setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
</programlisting>
    Replace <literal>/usr/local/pgsql/lib</> with whatever you set
    <option><literal>--libdir</></> to in <xref linkend="configure">.
1180
    You should put these commands into a shell start-up file such as
1181
    <filename>/etc/profile</> or <filename>~/.bash_profile</>.  Some
Peter Eisentraut's avatar
Peter Eisentraut committed
1182
    good information about the caveats associated with this method can
1183
    be found at <ulink
1184
    url="http://www.visi.com/~barr/ldpath.html"></ulink>.
1185 1186
   </para>

1187
   <para>
1188
    On some systems it might be preferable to set the environment
1189 1190 1191 1192
    variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis>
    building.
   </para>

1193
   <para>
1194 1195 1196 1197
    On <systemitem class="osname">Cygwin</systemitem>, put the library
    directory on the <envar>PATH</envar> or move the
    <filename>.dll</filename> files into the <filename>bin/</filename>
    directory.
1198
   </para>
1199

1200
   <para>
1201 1202
    If in doubt, refer to the manual pages of your system (perhaps
    <command>ld.so</command> or <command>rld</command>). If you later
1203 1204 1205 1206 1207 1208 1209
    on get a message like
<screen>
psql: error in loading shared libraries
libpq.so.2.1: cannot open shared object file: No such file or directory
</screen>
    then this step was necessary.  Simply take care of it then.
   </para>
1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232

   <para>
    <indexterm>
     <primary>ldconfig</primary>
    </indexterm>
    If you are on <systemitem class="osname">BSD/OS</>, <systemitem
    class="osname">Linux</>, or <systemitem class="osname">SunOS 4</>
    and you have root access you can run
<programlisting>
/sbin/ldconfig /usr/local/pgsql/lib
</programlisting>
    (or equivalent directory) after installation to enable the
    run-time linker to find the shared libraries faster.  Refer to the
    manual page of <command>ldconfig</> for more information.  On
    <systemitem class="osname">FreeBSD</>, <systemitem
    class="osname">NetBSD</>, and <systemitem
    class="osname">OpenBSD</> the command is
<programlisting>
/sbin/ldconfig -m /usr/local/pgsql/lib
</programlisting>
    instead.  Other systems are not known to have an equivalent
    command.
   </para>
1233 1234 1235 1236
  </sect2>

  <sect2>
   <title>Environment Variables</title>
1237 1238 1239 1240 1241

   <indexterm>
    <primary><envar>PATH</envar></primary>
   </indexterm>

1242 1243
   <para>
    If you installed into <filename>/usr/local/pgsql</> or some other
1244
    location that is not searched for programs by default, you should
1245
    add <filename>/usr/local/pgsql/bin</> (or whatever you set
1246
    <option><literal>--bindir</></> to in <xref linkend="configure">)
1247 1248 1249 1250 1251 1252 1253 1254 1255
    into your <envar>PATH</>.  Strictly speaking, this is not
    necessary, but it will make the use of PostgreSQL much more
    convenient.
   </para>

   <para>
    To do this, add the following to your shell start-up file, such as
    <filename>~/.bash_profile</> (or <filename>/etc/profile</>, if you
    want it to affect every user):
1256
<programlisting>
1257
PATH=/usr/local/pgsql/bin:$PATH
1258
export PATH
1259
</programlisting>
1260
    If you are using <command>csh</> or <command>tcsh</>, then use this command:
1261
<programlisting>
Bruce Momjian's avatar
Bruce Momjian committed
1262
set path = ( /usr/local/pgsql/bin $path )
1263 1264 1265 1266
</programlisting>
   </para>

   <para>
1267 1268 1269 1270
    <indexterm>
     <primary><envar>MANPATH</envar></primary>
     <seealso>man pages</seealso>
    </indexterm>
1271 1272
    To enable your system to find the <application>man</>
    documentation, you need to add a line like the following to a
1273 1274
    shell start-up file unless you installed into a location that is
    searched by default.
1275
<programlisting>
1276
MANPATH=/usr/local/pgsql/man:$MANPATH
1277
export MANPATH
1278 1279 1280 1281 1282 1283 1284 1285
</programlisting>
   </para>

   <para>
    The environment variables <envar>PGHOST</> and <envar>PGPORT</>
    specify to client applications the host and port of the database
    server, overriding the compiled-in defaults. If you are going to
    run client applications remotely then it is convenient if every
1286 1287
    user that plans to use the database sets <envar>PGHOST</>.  This
    is not required, however: the settings can be communicated via command
1288 1289 1290 1291
    line options to most client programs.
   </para>
  </sect2>
 </sect1>
1292

1293

1294
<![%standalone-include;[
1295
 <sect1 id="install-getting-started">
1296
  <title>Getting Started</title>
1297 1298

  <para>
1299 1300 1301
   The following is a quick summary of how to get <productname>PostgreSQL</> up and
   running once installed. The <citetitle>Administrator's Guide</>
   contains more information.
1302
  </para>
1303

1304 1305 1306
  <procedure>
   <step>
    <para>
1307 1308 1309 1310 1311 1312 1313
     Create a user account for the <productname>PostgreSQL</>
     server. This is the user the server will run as. For production
     use you should create a separate, unprivileged account
     (<quote>postgres</> is commonly used). If you do not have root
     access or just want to play around, your own user account is
     enough, but running the server as root is a security risk and
     will not work.
1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362
<screen>
<userinput>adduser postgres</>
</screen>
    </para>
   </step>

   <step>
    <para>
     Create a database installation with the <command>initdb</>
     command. To run <command>initdb</> you must be logged in to your
     <productname>PostgreSQL</> server account. It will not work as
     root.
<screen>
root# <userinput>mkdir /usr/local/pgsql/data</>
root# <userinput>chown postgres /usr/local/pgsql/data</>
root# <userinput>su - postgres</>
postgres$ <userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</>
</screen>
    </para>

    <para>
     The <option>-D</> option specifies the location where the data
     will be stored. You can use any path you want, it does not have
     to be under the installation directory. Just make sure that the
     server account can write to the directory (or create it, if it
     doesn't already exist) before starting <command>initdb</>, as
     illustrated here.
    </para>
   </step>

   <step>
    <para>
     The previous step should have told you how to start up the
     database server. Do so now. The command should look something
     like
<programlisting>
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
</programlisting>
     This will start the server in the foreground. To put the server
     in the background use something like
<programlisting>
nohup /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data \
    &lt;/dev/null &gt;&gt;server.log 2&gt;&amp;1 &lt;/dev/null &amp;
</programlisting>
    </para>

    <para>
     To stop a server running in the background you can type
<programlisting>
Peter Eisentraut's avatar
typos  
Peter Eisentraut committed
1363
kill `cat /usr/local/pgsql/data/postmaster.pid`
1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390
</programlisting>
    </para>

    <para>
     In order to allow TCP/IP connections (rather than only Unix
     domain socket ones) you need to pass the <option>-i</> option to
     <filename>postmaster</>.
    </para>
   </step>

   <step>
    <para>
     Create a database:
<screen>
<userinput>createdb testdb</>
</screen>
     Then enter
<screen>
<userinput>psql testdb</>
</screen>
     to connect to that database. At the prompt you can enter SQL
     commands and start experimenting.
    </para>
   </step>
  </procedure>
 </sect1>

1391
 <sect1 id="install-whatnow">
1392 1393 1394 1395 1396 1397
  <title>What Now?</title>

  <para>
   <itemizedlist>
    <listitem>
     <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1398 1399 1400 1401 1402
      The <productname>PostgreSQL</> distribution contains a
      comprehensive documentation set, which you should read sometime.
      After installation, the documentation can be accessed by
      pointing your browser to
      <filename>/usr/local/pgsql/doc/html/index.html</>, unless you
1403 1404 1405 1406
      changed the installation directories.
     </para>

     <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1407 1408
      The <citetitle>Tutorial</> should be your first reading if you
      are completely new to <acronym>SQL</> databases.
1409 1410 1411
      If you are familiar with database concepts then you want to
      proceed with the <citetitle>Administrator's Guide</citetitle>,
      which contains information about how to set up the database
Peter Eisentraut's avatar
Peter Eisentraut committed
1412
      server, database users, and authentication.
1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423
     </para>
    </listitem>

    <listitem>
     <para>
      Usually, you will want to modify your computer so that it will
      automatically start the database server whenever it boots. Some
      suggestions for this are in the <citetitle>Administrator's
      Guide</citetitle>.
     </para>
    </listitem>
1424

1425 1426 1427 1428 1429 1430 1431 1432
    <listitem>
     <para>
      Run the regression tests against the installed server (using the
      sequential test method). If you didn't run the tests before
      installation, you should definitely do it now. This is also
      explained in the <citetitle>Administrator's Guide</citetitle>.
     </para>
    </listitem>
1433

1434 1435 1436 1437
   </itemizedlist>
  </para>

<!-- do we still ship this? -->
1438
<!--
1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457
  <para>
   The documentation is also available in Postscript format. If you
   have a Postscript printer, or have your machine already set up to
   accept Postscript files using a print filter, then to print, for
   example the <citetitle>User's Guide</> simply type
<programlisting>
cd /usr/local/pgsql/doc
gunzip -c user.ps.gz | lpr
</programlisting>
   Here is how you might do it if you have <productname>Ghostscript</>
   installed on your system and are writing to a Laserjet printer.
<programlisting>
gunzip -c user.ps.gz \
    | gs -sDEVICE=laserjet -r300 -q -dNOPAUSE -sOutputFile=- \
    | lpr
</programlisting>
   Printer setups can vary wildly from system to system. If in doubt,
   consult your manuals or your local expert.
  </para>
1458 1459
-->

1460 1461 1462 1463 1464 1465 1466 1467
 </sect1>
]]>


 <sect1 id="supported-platforms">
  <title>Supported Platforms</title>

  <para>
1468 1469 1470 1471 1472
   <productname>PostgreSQL</> has been verified by the developer
   community to work on the platforms listed below. A supported
   platform generally means that <productname>PostgreSQL</> builds and
   installs according to these instructions and that the regression
   tests pass.
1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484
  </para>

  <note>
   <para>
    If you are having problems with the installation on a supported
    platform, please write to <email>pgsql-bugs@postgresql.org</email>
    or <email>pgsql-ports@postgresql.org</email>, not to the people
    listed here.
   </para>
  </note>

    <informaltable>
1485
     <tgroup cols="5">
1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496
      <thead>
       <row>
	<entry><acronym>OS</acronym></entry>
	<entry>Processor</entry>
	<entry>Version</entry>
	<entry>Reported</entry>
	<entry>Remarks</entry>
       </row>
      </thead>
      <tbody>
       <row>
1497
	<entry><systemitem class="osname">AIX</></entry>
1498
	<entry><systemitem>RS6000</></entry>
1499
	<entry>7.2</entry>
1500 1501 1502 1503
	<entry>2001-12-19,
	 Andreas Zeugswetter (<email>ZeugswetterA@spardat.at</email>),
	 Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
        <entry>see also <filename>doc/FAQ_AIX</filename></entry>
1504
       </row>
1505
       <row>
1506
	<entry><systemitem class="osname">BeOS</></entry>
1507
	<entry><systemitem>x86</></entry>
1508 1509 1510 1511
	<entry>7.2</entry>
	<entry>2001-11-29,
	 Cyril Velter (<email>cyril.velter@libertysurf.fr</email>)</entry>
        <entry>5.0.4</entry>
1512
       </row>
1513
       <row>
1514
	<entry><systemitem class="osname">BSD/OS</></entry>
1515
	<entry><systemitem>x86</></entry>
1516
	<entry>7.2</entry>
1517 1518 1519
	<entry>2001-11-27,
	 Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
        <entry>4.2</entry>
1520
       </row>
1521 1522 1523 1524 1525 1526 1527 1528
       <row>
	<entry><systemitem class="osname">FreeBSD</></entry>
	<entry><systemitem>Alpha</></entry>
	<entry>7.2</entry>
	<entry>2001-12-18,
	 Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
        <entry></entry>
       </row>
1529
       <row>
1530
	<entry><systemitem class="osname">FreeBSD</></entry>
1531
	<entry><systemitem>x86</></entry>
1532
	<entry>7.2</entry>
1533 1534
	<entry>2001-11-14,
	 Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
1535
        <entry></entry>
1536 1537
       </row>
       <row>
1538 1539
	<entry><systemitem class="osname">HP-UX</></entry>
	<entry><systemitem>PA-RISC</></entry>
1540
	<entry>7.2</entry>
1541 1542 1543 1544
        <entry>2001-11-29,
	 Joseph Conway (<email>Joseph.Conway@home.com</email>),
	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
        <entry>11.00 and 10.20; see also <filename>doc/FAQ_HPUX</filename></entry>
1545
       </row>
1546
       <row>
1547
	<entry><systemitem class="osname">IRIX</></entry>
1548
	<entry><systemitem>MIPS</></entry>
1549 1550 1551 1552
	<entry>7.2</entry>
	<entry>2001-11-28,
	 Luis Amigo (<email>lamigo@atc.unican.es</email>)</entry>
	<entry>6.5.13, MIPSPro 7.30</entry>
1553 1554
       </row>
       <row>
1555
	<entry><systemitem class="osname">Linux</></entry>
1556
	<entry><systemitem>Alpha</></entry>
1557
	<entry>7.2</entry>
1558 1559 1560
	<entry>2001-11-16,
	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
	<entry>2.2.18; tested at SourceForge</entry>
1561 1562
       </row>
       <row>
1563
	<entry><systemitem class="osname">Linux</></entry>
1564
	<entry><systemitem>armv4l</></entry>
1565 1566 1567
	<entry>7.2</entry>
	<entry>2001-12-10,
	 Mark Knox (<email>segfault@hardline.org</email>)</entry>
1568
	<entry>2.2.x</entry>
1569 1570
       </row>
       <row>
1571
	<entry><systemitem class="osname">Linux</></entry>
1572
	<entry><systemitem>MIPS</></entry>
1573
	<entry>7.2</entry>
1574 1575 1576
	<entry>2001-11-15,
	 Hisao Shibuya (<email>shibuya@alpha.or.jp</>)</entry>
	<entry>2.0.x; <productname>Cobalt Qube2</></entry>
1577
       </row>
1578 1579
       <row>
	<entry><systemitem class="osname">Linux</></entry>
1580
	<entry><systemitem>PlayStation 2</></entry>
1581 1582 1583 1584 1585
	<entry>7.2</entry>
	<entry>2001-12-12,
	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
	<entry>#undef HAS_TEST_AND_SET, slock_t</entry>
       </row>
1586
       <row>
1587
	<entry><systemitem class="osname">Linux</></entry>
1588
	<entry><systemitem>PPC74xx</></entry>
1589
	<entry>7.2</entry>
1590 1591 1592
	<entry>2001-11-16,
	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
	<entry>2.2.18; Apple G3</entry>
1593 1594
       </row>
       <row>
1595 1596
	<entry><systemitem class="osname">Linux</></entry>
	<entry><systemitem>S/390</></entry>
1597 1598 1599
	<entry>7.2</entry>
	<entry>2001-12-12,
	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
1600
	<entry></entry>
1601
       </row>
1602
       <row>
1603
	<entry><systemitem class="osname">Linux</></entry>
1604
	<entry><systemitem>Sparc</></entry>
1605 1606 1607 1608
	<entry>7.2</entry>
	<entry>2001-11-28, 
	 Doug McNaught (<email>doug@wireboard.com</email>)</entry>
	<entry>2.2.19</entry>
1609
       </row>
1610
       <row>
1611 1612
	<entry><systemitem class="osname">Linux</></entry>
	<entry><systemitem>x86</></entry>
1613
	<entry>7.2</entry>
1614 1615
	<entry>2001-11-15,
	 Thomas Lockhart (<email>lockhart@fourpalms.org</email>)</entry>
1616
	<entry>2.0.x, 2.2.x, 2.4.x</entry>
1617
       </row>
1618
       <row>
1619 1620
	<entry><systemitem class="osname">MacOS X</></entry>
	<entry><systemitem>PPC</></entry>
1621
	<entry>7.2</entry>
1622 1623
	<entry>2001-11-28,
	 Gavin Sherry (<email>swm@linuxworld.com.au</email>)</entry>
1624
	<entry>10.1.x</entry>
1625
       </row>
1626
       <row>
1627
	<entry><systemitem class="osname">NetBSD</></entry>
1628
	<entry><systemitem>Alpha</></entry>
1629
	<entry>7.2</entry>
1630 1631 1632
	<entry>2001-11-20,
	 Thomas Thai (<email>tom@minnesota.com</email>)</entry>
	<entry>1.5W</entry>
1633 1634
       </row>
       <row>
1635
	<entry><systemitem class="osname">NetBSD</></entry>
1636
	<entry><systemitem>arm32</></entry>
1637
	<entry>7.1</entry>
1638 1639 1640
	<entry>2001-03-21,
	 Patrick Welche (<email>prlw1@cam.ac.uk</email>)</entry>
	<entry>1.5E</entry>
1641
       </row>
1642
       <row>
1643 1644
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>m68k</></entry>
1645
	<entry>7.0</entry>
1646 1647
	<entry>2000-04-10,
	 Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
1648 1649
	<entry>Mac 8xx</entry>
       </row>
1650 1651 1652 1653 1654 1655 1656 1657
      <row>
       <entry><systemitem class="osname">NetBSD</></entry>
       <entry><systemitem>MIPS</></entry>
       <entry>7.2.1</entry>
       <entry>2002-06-13,
        Warwick Hunter (<email>whunter@agile.tv</email>)</entry>
       <entry>1.5.3</entry>
      </row>
1658
       <row>
1659 1660
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>PPC</></entry>
1661 1662 1663 1664
	<entry>7.2</entry>
	<entry>2001-11-28,
	 Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
	<entry>1.5</entry>
1665
       </row>
1666
       <row>
1667 1668
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>Sparc</></entry>
1669 1670 1671
	<entry>7.2</entry>
	<entry>2001-12-03,
	 Matthew Green (<email>mrg@eterna.com.au</email>)</entry>
1672
	<entry>32- and 64-bit builds</entry>
1673
       </row>
1674
       <row>
1675
        <entry><systemitem class="osname">NetBSD</></entry>
1676
        <entry><systemitem>VAX</></entry>
1677
        <entry>7.1</entry>
1678 1679 1680
        <entry>2001-03-30,
	 Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
        <entry>1.5</entry>
1681 1682
       </row>
       <row>
1683
	<entry><systemitem class="osname">NetBSD</></entry>
1684
	<entry><systemitem>x86</></entry>
1685 1686 1687 1688
	<entry>7.2</entry>
	<entry>2001-11-28,
	 Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
	<entry>1.5</entry>
1689 1690
       </row>
       <row>
1691
	<entry><systemitem class="osname">OpenBSD</></entry>
1692
	<entry><systemitem>Sparc</></entry>
1693 1694 1695
	<entry>7.2</entry>
	<entry>2001-11-27,
	 Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
1696
        <entry>3.0</entry>
1697
       </row>
1698
       <row>
1699
	<entry><systemitem class="osname">OpenBSD</></entry>
1700
	<entry><systemitem>x86</></entry>
1701 1702 1703
	<entry>7.2</entry>
	<entry>2001-11-26,
	 Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
1704
        <entry>3.0</entry>
1705
       </row>
1706
       <row>
1707
	<entry><systemitem class="osname">Open UNIX</></entry>
1708
	<entry><systemitem>x86</></entry>
1709 1710 1711 1712 1713
	<entry>7.2</entry>
	<entry>2001-11-28,
	 OU-8 Larry Rosenman (<email>ler@lerctr.org</email>),
	 UW-7 Olivier Prenant (<email>ohp@pyrenet.fr</email>)</entry>
	<entry>see also <filename>doc/FAQ_SCO</filename></entry>
1714
       </row>
1715
     <row>
1716
      <entry><systemitem class="osname">QNX 4 RTOS</></entry>
1717
      <entry><systemitem>x86</></entry>
1718 1719
      <entry>7.2</entry>
      <entry>2001-12-10,
1720 1721
       Bernd Tegge (<email>tegge@repas-aeg.de</email>)
      </entry>
1722
      <entry>4.25; see also <filename>doc/FAQ_QNX4</filename></entry>
1723
     </row>
1724
       <row>
1725
	<entry><systemitem class="osname">Solaris</></entry>
1726
	<entry><systemitem>Sparc</></entry>
1727
	<entry>7.2</entry>
1728 1729
	<entry>2001-11-12,
	 Andrew Sullivan (<email>andrew@libertyrms.com</email>)</entry>
1730
	<entry>2.6-8; see also <filename>doc/FAQ_Solaris</filename></entry>
1731 1732
       </row>
       <row>
1733
	<entry><systemitem class="osname">Solaris</></entry>
1734
	<entry><systemitem>x86</></entry>
1735 1736 1737 1738
	<entry>7.2</entry>
	<entry>2001-11-28, 
	 Martin Renters (<email>martin@datafax.com</email>)</entry>
	<entry>2.8; see also <filename>doc/FAQ_Solaris</filename></entry>
1739
       </row>
1740
      <row>
1741
       <entry><systemitem class="osname">SunOS 4</></entry>
1742 1743 1744 1745 1746
       <entry><systemitem>Sparc</></entry>
       <entry>7.2</entry>
       <entry>2001-12-04, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
       <entry></entry>
      </row>
1747
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1748
	<entry><systemitem class="osname">Tru64 UNIX</></entry>
1749
	<entry><systemitem>Alpha</></entry>
1750 1751
	<entry>7.2</entry>
	<entry>2001-11-26,
1752 1753 1754
	 Alessio Bragadini (<email>alessio@albourne.com</email>),
         Bernd Tegge (<email>tegge@repas-aeg.de</email>)</entry>
        <entry>5.0; 4.0g with cc and gcc</entry>
1755 1756
       </row>
       <row>
1757
	<entry><systemitem class="osname">Windows</></entry>
1758
	<entry><systemitem>x86</></entry>
1759 1760 1761
	<entry>7.2</entry>
	<entry>2001-12-13,
	 Dave Page (<email>dpage@vale-housing.co.uk</email>),
1762
	 Jason Tishler (<email>jason@tishler.net</email>)</entry>
1763
        <entry>with <application>Cygwin</application>; see <filename>doc/FAQ_MSWIN</filename></entry>
1764
       </row>
1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776
      <row>
       <entry><systemitem class="osname">Windows</></entry>
       <entry><systemitem>x86</></entry>
       <entry>7.2</entry>
       <entry>2001-12-10,
	Dave Page (<email>dpage@vale-housing.co.uk</email>)</entry>
       <entry>
	native is client-side only;
<![%standalone-include[see Administrator's Guide]]>
<![%standalone-ignore[see <xref linkend="install-win32">]]>
       </entry>
      </row>
1777 1778 1779 1780 1781
      </tbody>
     </tgroup>
    </informaltable>

  <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1782
   <title>Unsupported Platforms:</title>
1783
   <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1784 1785 1786 1787
    The following platforms are either known not to work, or they used
    to work in a previous release and we did not receive explicit
    confirmation of a successful test with version &majorversion; at
    the time this list was compiled.  We include these here to let you
1788 1789 1790 1791 1792 1793
    know that these platforms <emphasis>could</> be supported if given
    some attention.
   </para>
  </formalpara>

  <informaltable>
1794
   <tgroup cols="5">
1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806
    <thead>
     <row>
      <entry><acronym>OS</acronym></entry>
      <entry>Processor</entry>
      <entry>Version</entry>
      <entry>Reported</entry>
      <entry>Remarks</entry>
     </row>
    </thead>

    <tbody>
     <row>
1807
      <entry><systemitem class="osname">DG/UX 5.4R4.11</></entry>
1808
      <entry><systemitem>m88k</></entry>
1809
      <entry>6.3</entry>
1810
      <entry>1998-03-01, Brian E Gallew (<email>geek+@cmu.edu</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1811
      <entry>no recent reports</entry>
1812
     </row>
1813
     <row>
1814 1815
      <entry><systemitem class="osname">MkLinux DR1</></entry>
      <entry><systemitem>PPC750</></entry>
1816 1817 1818 1819
      <entry>7.0</entry>
      <entry>2001-04-03, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
      <entry>7.1 needs OS update?</entry>
     </row>
1820
     <row>
1821
      <entry><systemitem class="osname">NeXTSTEP</></entry>
1822
      <entry><systemitem>x86</></entry>
1823 1824
      <entry>6.x</entry>
      <entry>1998-03-01, David Wetzel (<email>dave@turbocat.de</email>)</entry>
1825
      <entry>bit rot suspected</entry>
1826
     </row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1827
     <row>
1828
      <entry><systemitem class="osname">QNX RTOS v6</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1829 1830 1831
      <entry><systemitem>x86</></entry>
      <entry>7.2</entry>
      <entry>2001-11-20, Igor Kovalenko (<email>Igor.Kovalenko@motorola.com</email>)</entry>
1832
      <entry>patches available in archives, but too late for 7.2</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1833
     </row>
1834
     <row>
1835 1836
      <entry><systemitem class="osname">SCO OpenServer 5</></entry>
      <entry><systemitem>x86</></entry>
1837 1838
      <entry>6.5</entry>
      <entry>1999-05-25, Andrew Merrill (<email>andrew@compclass.com</>)</entry>
1839
      <entry>&version; should work, but no reports; see also <filename>doc/FAQ_SCO</filename></entry>
1840
     </row>
1841
     <row>
1842 1843
      <entry><systemitem class="osname">System V R4</></entry>
      <entry><systemitem>m88k</></entry>
1844
      <entry>6.2.1</entry>
1845
      <entry>1998-03-01, Doug Winterburn (<email>dlw@seavme.xroads.com</email>)</entry>
1846
      <entry>needs new <acronym>TAS</acronym> spinlock code</entry>
1847 1848
     </row>
     <row>
1849 1850
      <entry><systemitem class="osname">System V R4</></entry>
      <entry><systemitem>MIPS</></entry>
1851
      <entry>6.4</entry>
1852
      <entry>1998-10-28, Frank Ridderbusch (<email>ridderbusch.pad@sni.de</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1853
      <entry>no recent reports</entry>
1854 1855
     </row>
     <row>
1856 1857
      <entry><systemitem class="osname">Ultrix</></entry>
      <entry><systemitem>MIPS</></entry>
1858 1859
      <entry>7.1</entry>
      <entry>2001-03-26</entry>
1860
      <entry><acronym>TAS</acronym> spinlock code not detected</entry>
1861 1862
     </row>
     <row>
1863 1864
      <entry><systemitem class="osname">Ultrix</></entry>
      <entry><systemitem>VAX</></entry>
1865
      <entry>6.x</entry>
1866
      <entry>1998-03-01</entry>
1867
      <entry></entry>
1868
     </row>
1869 1870 1871 1872 1873 1874
    </tbody>
   </tgroup>
  </informaltable>
 </sect1>

</chapter>
1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892

<!-- 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-tabs-mode:nil
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:("/usr/share/sgml/catalog")
sgml-local-ecat-files:nil
End:
-->