installation.sgml 65.4 KB
Newer Older
1
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.185 2003/11/26 15:56:48 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
 <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
12 13
  This <![%standalone-include;[document]]>
  <![%standalone-ignore;[chapter]]> describes the installation of
14 15 16 17
  <productname>PostgreSQL</productname> from the source code
  distribution.
 </para>

18
 <sect1 id="install-short">
19 20 21
  <title>Short Version</title>

  <para>
22
<synopsis>
23 24
./configure
gmake
25
su
26 27
gmake install
adduser postgres
28 29
mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data
30 31 32 33 34
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
35
</synopsis>
36
   The long version is the rest of this
37 38
   <![%standalone-include;[document.]]>
   <![%standalone-ignore;[chapter.]]>
39 40
  </para>
 </sect1>
41 42


43
 <sect1 id="install-requirements">
44
  <title>Requirements</title>
45

46 47
  <para>
   In general, a modern Unix-compatible platform should be able to run
48
   <productname>PostgreSQL</>.
49
    The platforms that had received specific testing at the
50 51 52 53 54 55
   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>

56
  <para>
57 58 59
   The following software packages are required for building
   <productname>PostgreSQL</>:

60 61 62
   <itemizedlist>
    <listitem>
     <para>
63 64 65 66
      <indexterm>
       <primary>make</primary>
      </indexterm>

67 68 69 70
      <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
Bruce Momjian's avatar
Bruce Momjian committed
71
      refer to it by that name. (On some systems
72
      <acronym>GNU</acronym> <application>make</> is the default tool with the name
Bruce Momjian's avatar
Bruce Momjian committed
73 74
      <filename>make</>.) To test for <acronym>GNU</acronym>
      <application>make</application> enter
75 76 77
<screen>
<userinput>gmake --version</userinput>
</screen>
Peter Eisentraut's avatar
Peter Eisentraut committed
78
      It is recommended to use version 3.76.1 or later.
79 80
     </para>
    </listitem>
81

82 83 84 85 86 87 88 89 90 91
    <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>
92 93
     <para>
      <application>gzip</> is needed to unpack the distribution in the
94 95
      first place.<![%standalone-include;[  If you are reading this, you probably already got
      past that hurdle.]]>
96
     </para>
97 98 99 100
    </listitem>

    <listitem>
     <para>
101 102 103 104
      <indexterm>
       <primary>readline</primary>
      </indexterm>

105 106 107 108 109 110
      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
111
      <productname>Readline</productname>-compatible and is used if
112
      <filename>libreadline</filename> is not found.)
113 114 115 116 117
     </para>
    </listitem>

    <listitem>
     <para>
118
      <indexterm>
119 120
       <primary>installation</primary>
       <secondary>on Windows</secondary>
121 122
      </indexterm>

123 124 125 126
      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.
127 128
     </para>
    </listitem>
129 130
   </itemizedlist>
  </para>
131

132 133 134 135 136 137 138 139 140
  <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
Bruce Momjian's avatar
Bruce Momjian committed
141 142 143 144
      <productname>Perl</productname> installation, including the
      <filename>libperl</filename> library and the header files.
      Since PL/Perl will be a shared library, the
      <indexterm><primary>libperl</primary></indexterm>
145
      <filename>libperl</filename> library must be a shared library
146 147 148 149
      also on most platforms.  This appears to be the default in
      recent Perl versions, but it was not in earlier versions, and in
      general it is the choice of whomever installed Perl at your
      site.
150 151 152
     </para>

     <para>
153 154
      If you don't have the shared library but you need one, a message
      like this will appear during the build to point out this fact:
155 156 157 158 159
<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>
160
      (If you don't follow the on-screen output you will merely notice
161 162 163 164 165 166
      that the PL/Perl library object, <filename>plperl.so</filename>
      or similar, will not be installed.)  If you see this, you will
      have to rebuild 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.
167 168 169 170 171
     </para>
    </listitem>

    <listitem>
     <para>
172 173 174
      To build the PL/Python server programming language, you need a
      Python installation, including the header files.  Since
      PL/Python will be a shared library, the
175 176 177
      <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
178 179 180 181 182 183 184 185
      Python installation.
     </para>

     <para>
      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:
186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201
<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
Bruce Momjian's avatar
Bruce Momjian committed
202 203
      the <productname>PostgreSQL</> build system of this.  Consult
      the <filename>Makefile</filename> in the
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 242 243 244 245 246 247 248 249 250 251 252 253
      <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
Bruce Momjian's avatar
Bruce Momjian committed
254 255 256 257 258 259
      other than English, you need an implementation of the
      <application>Gettext</> <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
260
      url="http://www.postgresql.org/~petere/gettext.html" ></ulink>.
261
      If you are using the <application>Gettext</> implementation in
Bruce Momjian's avatar
Bruce Momjian committed
262 263 264 265
      the <acronym>GNU</acronym> 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.
266 267 268 269 270
     </para>
    </listitem>

    <listitem>
     <para>
271
      <application>Kerberos</>, <application>OpenSSL</>, or <application>PAM</>,
272
      if you want to support authentication using these services.
273 274 275 276 277 278
     </para>
    </listitem>
   </itemizedlist>
  </para>

  <para>
279
   If you are building from a <acronym>CVS</acronym> tree instead of
Bruce Momjian's avatar
Bruce Momjian committed
280 281
   using a released source package, or if you want to do development,
   you also need the following packages:
282 283

   <itemizedlist>
284 285
    <listitem>
     <para>
286
      <indexterm>
287 288 289 290 291 292 293
       <primary>flex</primary>
      </indexterm>
      <indexterm>
       <primary>bison</primary>
      </indexterm>
      <indexterm>
       <primary>yacc</primary>
294 295
      </indexterm>

296
      <application>Flex</> and <application>Bison</>
297 298 299
      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
Bruce Momjian's avatar
Bruce Momjian committed
300
      <application>Bison</> 1.875 or later. Other <application>yacc</>
301 302 303
      programs can sometimes be used, but doing so requires extra
      effort and is not recommended. Other <application>lex</>
      programs will definitely not work.
304 305
     </para>
    </listitem>
306 307
   </itemizedlist>
  </para>
308

309 310 311
  <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
312
   url="http://www.gnu.org/order/ftp.html"></>
313
   for a list) or at <ulink
314
   url="ftp://ftp.gnu.org/gnu/"></ulink>.
315 316 317 318
  </para>

  <para>
   Also check that you have sufficient disk space. You will need about
319 320 321 322 323 324 325
   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.
326
  </para>
327
 </sect1>
328

329
<![%standalone-ignore;[
330
 <sect1 id="install-getsource">
331
  <title>Getting The Source</title>
332

333
  <para>
334 335
   The <productname>PostgreSQL</> &version; sources can be obtained by
   anonymous FTP from <ulink
Peter Eisentraut's avatar
Peter Eisentraut committed
336
   url="ftp://ftp.postgresql.org/pub/source/v&version;/postgresql-&version;.tar.gz"></ulink>.
Peter Eisentraut's avatar
Peter Eisentraut committed
337
   Use a mirror if possible. After you have obtained the file, unpack it:
338 339 340 341 342
<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
343 344 345
   <filename>postgresql-&version;</filename> under the current directory
   with the <productname>PostgreSQL</> sources.
   Change into that directory for the rest
346 347 348 349 350 351 352 353
   of the installation procedure.
  </para>
 </sect1>
]]>

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

354 355 356 357
  <indexterm zone="install-upgrading">
   <primary>upgrading</primary>
  </indexterm>

358 359
  <para>
   The internal data storage format changes with new releases of
360 361
   <productname>PostgreSQL</>. Therefore, if you are upgrading an
   existing installation that does not have a version number
362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382
   <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>
383 384
     <indexterm>
      <primary>pg_dumpall</primary>
Peter Eisentraut's avatar
Peter Eisentraut committed
385
      <secondary>use during upgrade</secondary>
386 387
     </indexterm>

388
     To back up your database installation, type:
389 390 391
<screen>
<userinput>pg_dumpall &gt; <replaceable>outputfile</></userinput>
</screen>
392
     If you need to preserve OIDs (such as when using them as
393
     foreign keys), then use the <option>-o</option> option when running
394 395 396 397 398
     <command>pg_dumpall</>.
    </para>

    <para>
     <command>pg_dumpall</command> does not
399
     save large objects.  Check
400
     <![%standalone-include[the documentation]]>
401
     <![%standalone-ignore[<xref linkend="backup-dump-caveats">]]>
402
     if you need to do this.
403 404 405
    </para>

    <para>
406 407 408
     To make the backup, you can use the <command>pg_dumpall</command>
     command from the version you are currently running.  For best
     results, however, try to use the <command>pg_dumpall</command>
409 410 411 412 413 414 415 416
     command from <productname>PostgreSQL</productname> &version;,
     since this version contains bug fixes and improvements over older
     versions.  While this advice might seem idiosyncratic since you
     haven't installed the new version yet, it is advisable to follow
     it if you plan to install the new version in parallel with the
     old version.  In that case you can complete the installation
     normally and transfer the data later.  This will also decrease
     the downtime.
417 418
    </para>
   </step>
419

420 421 422 423 424 425 426 427 428 429
   <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
430
     you must find out the process ID of the server yourself, for
431 432 433 434 435
     example by typing <userinput>ps ax | grep postmaster</>, and
     supply it to the <command>kill</> command.
    </para>

    <para>
436
     On systems that have <productname>PostgreSQL</> started at boot time, there is
437
     probably a start-up file that will accomplish the same thing. For
438
     example, on a <systemitem class="osname">Red Hat Linux</> system one might find that
439
<screen>
440
<userinput>/etc/rc.d/init.d/postgresql stop</userinput>
441
</screen>
442
     works.  Another possibility is <userinput>pg_ctl stop</>.
443 444 445 446 447 448 449
    </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
450 451
     way, in case you have trouble and need to revert to it.
     Use a command like this:
452 453 454 455 456 457 458 459 460 461 462 463 464
<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
465 466
<userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</>
<userinput>/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data</>
467 468 469 470 471 472 473
</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>
474 475

  <para>
476
   These topics are discussed at length in <![%standalone-include[the
477
   documentation,]]> <![%standalone-ignore[<xref
478 479
   linkend="migration">,]]> which you are encouraged to read in any
   case.
480
  </para>
481 482 483
 </sect1>


484
 <sect1 id="install-procedure">
485 486 487 488 489 490
  <title>Installation Procedure</title>

  <procedure>

  <step id="configure">
   <title>Configuration</>
491 492 493 494 495

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

496
   <para>
Peter Eisentraut's avatar
typos  
Peter Eisentraut committed
497
    The first step of the installation procedure is to configure the
498 499
    source tree for your system and choose the options you would like.
    This is done by running the <filename>configure</> script. For a
500
    default installation simply enter
501 502 503 504 505
<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
506 507 508 509
    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.)
510 511 512 513
   </para>

   <para>
    The default configuration will build the server and utilities, as
514
    well as all client applications and interfaces that require only a
515 516 517 518 519
    C compiler. All files will be installed under
    <filename>/usr/local/pgsql</> by default.
   </para>

   <para>
520
    You can customize the build and installation process by supplying one
521 522 523 524 525
    or more of the following command line options to
    <filename>configure</filename>:

     <variablelist>
      <varlistentry>
526
       <term><option>--prefix=<replaceable>PREFIX</></option></term>
527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543
       <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>
544
       <term><option>--exec-prefix=<replaceable>EXEC-PREFIX</></option></term>
545 546 547 548 549 550 551
       <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
552
         <replaceable>PREFIX</> and both architecture-dependent and
553 554 555 556 557 558 559
         independent files will be installed under the same tree,
         which is probably what you want.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
560
       <term><option>--bindir=<replaceable>DIRECTORY</></option></term>
561 562 563 564 565 566 567 568 569 570
       <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>
571
       <term><option>--datadir=<replaceable>DIRECTORY</></option></term>
572 573 574 575 576 577 578 579 580 581 582
       <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>
583
       <term><option>--sysconfdir=<replaceable>DIRECTORY</></option></term>
584 585 586 587 588 589 590 591 592
       <listitem>
        <para>
         The directory for various configuration files,
         <filename><replaceable>PREFIX</>/etc</> by default.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
593
       <term><option>--libdir=<replaceable>DIRECTORY</></option></term>
594 595 596 597 598 599 600 601 602 603
       <listitem>
        <para>
         The location to install libraries and dynamically loadable
         modules. The default is
         <filename><replaceable>EXEC-PREFIX</>/lib</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
604
       <term><option>--includedir=<replaceable>DIRECTORY</></option></term>
605 606 607 608 609 610 611 612 613
       <listitem>
        <para>
         The directory for installing C and C++ header files. The
         default is <filename><replaceable>PREFIX</>/include</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
614
       <term><option>--mandir=<replaceable>DIRECTORY</></option></term>
615 616
       <listitem>
        <para>
617 618 619 620
         The man pages that come with <productname>PostgreSQL</> will be installed under
         this directory, in their respective
         <filename>man<replaceable>x</></> subdirectories.
         The default is <filename><replaceable>PREFIX</>/man</>.
621 622 623 624 625
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
626 627
       <term><option>--with-docdir=<replaceable>DIRECTORY</></option></term>
       <term><option>--without-docdir</option></term>
628 629
       <listitem>
        <para>
630 631 632 633 634 635 636
         Documentation files, except <quote>man</> pages, will be
         installed into this directory. The default is
         <filename><replaceable>PREFIX</>/doc</>.  If the option
         <option>--without-docdir</option> is specified, the
         documentation will not be installed by <command>make
         install</command>.  This is intended for packaging scripts
         that have special methods for installing documentation.
637 638 639
        </para>
       </listitem>
      </varlistentry>
Peter Eisentraut's avatar
Peter Eisentraut committed
640
     </variablelist>
641 642 643

     <note>
      <para>
644
       Care has been taken to make it possible to install <productname>PostgreSQL</> 
645 646 647 648 649 650 651
       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
652
       string <quote><literal>postgres</></quote> or <quote><literal>pgsql</></quote>.  For
653 654 655 656
       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
657
       in <filename>/opt/postgres/doc</filename>.  The public C header files of the
658 659 660 661
       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
662
       <varname>includedir</varname>.
663 664
       See the documentation of each interface for information about how to get at
       the its header files.
665 666
       Finally, a private subdirectory will also be created, if appropriate,
       under <varname>libdir</varname> for dynamically loadable modules.       
667 668 669
      </para>
     </note>
    </para>
670

671 672
    <para>
     <variablelist>
673
      <varlistentry>
674
       <term><option>--with-includes=<replaceable>DIRECTORIES</></option></term>
675 676 677 678 679
       <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
680
         (such as GNU <application>Readline</>) installed in a non-standard
Peter Eisentraut's avatar
Peter Eisentraut committed
681
         location,
682
         you have to use this option and probably also the corresponding
683 684 685 686 687 688 689 690 691
         <option>--with-libraries</> option.
        </para>
        <para>
         Example: <literal>--with-includes=/opt/gnu/include:/usr/sup/include</>.
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
692
       <term><option>--with-libraries=<replaceable>DIRECTORIES</></option></term>
693 694 695 696 697 698 699 700 701 702 703 704 705 706
       <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>

707
      <varlistentry>
708
       <term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term>
709 710
       <listitem>
        <para>
711 712 713 714 715 716 717 718 719 720
         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.
721 722 723 724
        </para>

        <para>
         To use this option, you will need an implementation of the
725
         <application>Gettext</> API; see above.
726 727 728 729
        </para>
       </listitem>
      </varlistentry>

730
      <varlistentry>
731
       <term><option>--with-pgport=<replaceable>NUMBER</></option></term>
732 733 734 735 736 737
       <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,
738
         which can be very convenient.  Usually the only good reason
Peter Eisentraut's avatar
Peter Eisentraut committed
739 740
         to select a non-default value is if you intend to run multiple
         <productname>PostgreSQL</> servers on the same machine.
741 742 743 744 745
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
746
       <term><option>--with-perl</option></term>
747 748
       <listitem>
        <para>
749
         Build the PL/Perl server-side language.
750 751 752 753 754
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
755
       <term><option>--with-python</option></term>
756 757
       <listitem>
        <para>
758
         Build the PL/Python server-side language.
759 760 761 762 763
        </para>
       </listitem>
      </varlistentry>

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

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

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

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

814
      <varlistentry>
Peter Eisentraut's avatar
Peter Eisentraut committed
815 816
       <term><option>--with-krb4<optional>=<replaceable>DIRECTORY</></></option></term>
       <term><option>--with-krb5<optional>=<replaceable>DIRECTORY</></></option></term>
817 818
       <listitem>
        <para>
819
         Build with support for Kerberos authentication. You can use
820 821 822 823
         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
824
         relevant header files and libraries are not under a common
825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841
         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>
842
       <term><option>--with-krb-srvnam=<replaceable>NAME</></option></term>
843 844 845
       <listitem>
        <para>
         The name of the Kerberos service principal.
846
         <literal>postgres</literal> is the default. There's probably no
847 848 849 850 851
         reason to change this.
        </para>
       </listitem>
      </varlistentry>

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

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

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

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

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

897 898 899 900
      <varlistentry>
       <term><option>--with-rendezvous</option></term>
       <listitem>
        <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
901
         Build with Rendezvous support.
902 903 904 905
        </para>
       </listitem>
      </varlistentry>

906
      <varlistentry>
907
       <term><option>--disable-spinlocks</option></term>
908 909
       <listitem>
        <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
910 911 912 913 914
         Allow the builds to succeed even if PostgreSQL has no CPU
         spinlock support for the platform.  The lack of spinlock
         support will result in poor performance; therefore, this
         option should only be used if the build aborts and informs
         you that the platform lacks spinlock support.
915 916 917 918
        </para>
       </listitem>
      </varlistentry>

919
      <varlistentry>
920
       <term><option>--enable-thread-safety</option></term>
921 922
       <listitem>
        <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
923 924 925 926
         Make the client libraries thread-safe.  This allows
         concurrent threads in <application>libpq</application> and
         <application>ECPG</application> programs to safely control
         their private connection handles.
927 928 929 930
        </para>
       </listitem>
      </varlistentry>

931 932 933 934
      <varlistentry>
       <term><option>--without-zlib</option></term>
       <listitem>
        <para>
935
         Prevents the use of the <application>Zlib</> library.  This disables
936 937 938 939 940 941 942
         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>

943
      <varlistentry>
944
       <term><option>--enable-debug</option></term>
945 946 947 948
       <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
949
         to analyze problems. This enlarges the size of the installed
Peter Eisentraut's avatar
Peter Eisentraut committed
950 951 952 953 954 955 956
         executables considerably, and on non-GCC compilers it usually
         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
         recommended for production installations only if you use GCC.
         But you should always have it on if you are doing development work
         or running a beta version.
Tom Lane's avatar
Tom Lane committed
957 958 959 960 961
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
962
       <term><option>--enable-cassert</option></term>
Tom Lane's avatar
Tom Lane committed
963 964
       <listitem>
        <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
965 966 967 968 969 970 971 972
         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
         still lead to server restarts if it triggers an assertion
         failure.  Currently, this option is not recommended for
Tom Lane's avatar
Tom Lane committed
973
         production use, but you should have it on for development work
Peter Eisentraut's avatar
Peter Eisentraut committed
974
         or when running a beta version.
975 976 977
        </para>
       </listitem>
      </varlistentry>
978 979 980 981 982

      <varlistentry>
       <term><option>--enable-depend</option></term>
       <listitem>
        <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
983 984 985 986 987 988
         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.
989 990 991 992
        </para>
       </listitem>
      </varlistentry>

993
     </variablelist>
994
    </para>
995

996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008
    <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:
1009
<screen>
1010
<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'</>
1011
</screen>
1012 1013
    </para>
   </step>
1014 1015 1016 1017 1018 1019 1020 1021 1022 1023

  <step>
   <title>Build</title>

   <para>
    To start the build, type
<screen>
<userinput>gmake</userinput>
</screen>
    (Remember to use <acronym>GNU</> <application>make</>.) The build
1024 1025
    may take anywhere from 5 minutes to half an hour depending on your
    hardware. The last line displayed should be
1026 1027 1028 1029 1030 1031 1032 1033 1034
<screen>
All of PostgreSQL is successfully made. Ready to install.
</screen>
   </para>
  </step>

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

1035 1036 1037 1038
   <indexterm>
    <primary>regression test</primary>
   </indexterm>

1039 1040 1041
   <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
1042 1043 1044
    tests are a test suite to verify that <productname>PostgreSQL</>
    runs on your machine in the way the developers expected it
    to. Type
1045
<screen>
1046
<userinput>gmake check</userinput>
1047
</screen>
1048
    (This won't work as root; do it as an unprivileged user.)
1049
    <![%standalone-include[The file
1050
    <filename>src/test/regress/README</> and the
1051
    documentation contain]]>
1052
    <![%standalone-ignore[<xref linkend="regress"> contains]]>
1053 1054
    detailed information about interpreting the test results. You can
    repeat this test at any later time by issuing the same command.
1055 1056 1057 1058 1059 1060 1061 1062 1063
   </para>
  </step>

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

   <note>
    <para>
     If you are upgrading an existing system and are going to install
1064
     the new files over the old ones, then you should have backed up
1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082
     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>

1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095
   <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>

1096
   <para>
1097
    The standard installation provides only the header files needed for client
1098
    application development.  If you plan to do any server-side program
1099
    development (such as custom functions or data types written in C),
1100 1101 1102 1103 1104
    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
1105
    This adds a megabyte or two to the installation footprint, and is only
1106 1107 1108 1109 1110
    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>

1111
   <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1112
    <title>Client-only installation:</title>
1113 1114
    <para>
     If you want to install only the client applications and
1115
     interface libraries, then you can use these commands:
1116 1117
<screen>
<userinput>gmake -C src/bin install</>
1118
<userinput>gmake -C src/include install</>
1119 1120 1121 1122 1123
<userinput>gmake -C src/interfaces install</>
<userinput>gmake -C doc install</>
</screen>
    </para>
   </formalpara>
1124 1125
  </step>
  </procedure>
1126

1127
  <formalpara>
1128
   <title>Uninstallation:</title>
1129 1130
   <para>
    To undo the installation use the command <command>gmake
1131
    uninstall</>. However, this will not remove any created directories.
1132
   </para>
1133
  </formalpara>
1134

1135 1136 1137 1138 1139 1140
  <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
1141
    clean</>. This will preserve the files made by the <command>configure</command>
1142 1143 1144 1145 1146 1147 1148
    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>
1149

1150
  <para>
1151 1152
   If you perform a build and then discover that your <command>configure</>
   options were wrong, or if you change anything that <command>configure</>
1153 1154 1155
   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
1156 1157
   may not propagate everywhere they need to.
  </para>
1158 1159
 </sect1>

1160
 <sect1 id="install-post">
1161 1162 1163 1164
  <title>Post-Installation Setup</title>

  <sect2>
   <title>Shared Libraries</title>
1165 1166

   <indexterm>
Peter Eisentraut's avatar
Peter Eisentraut committed
1167
    <primary>shared library</primary>
1168 1169
   </indexterm>

1170
   <para>
1171
    On some systems that have shared libraries (which most systems do)
1172
    you need to tell your system how to find the newly installed
1173
    shared libraries.  The systems on which this is
1174 1175 1176 1177 1178 1179 1180 1181
    <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</>.
1182 1183 1184 1185 1186 1187
   </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
1188
    shells (<command>sh</>, <command>ksh</>, <command>bash</>, <command>zsh</>)
1189 1190 1191 1192
<programlisting>
LD_LIBRARY_PATH=/usr/local/pgsql/lib
export LD_LIBRARY_PATH
</programlisting>
1193
    or in <command>csh</> or <command>tcsh</>
1194 1195 1196 1197 1198
<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">.
1199
    You should put these commands into a shell start-up file such as
1200
    <filename>/etc/profile</> or <filename>~/.bash_profile</>.  Some
Peter Eisentraut's avatar
Peter Eisentraut committed
1201
    good information about the caveats associated with this method can
1202
    be found at <ulink
1203
    url="http://www.visi.com/~barr/ldpath.html"></ulink>.
1204 1205
   </para>

1206
   <para>
1207
    On some systems it might be preferable to set the environment
1208 1209 1210 1211
    variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis>
    building.
   </para>

1212
   <para>
1213
    On <systemitem class="osname">Cygwin</systemitem>, put the library
1214
    directory in the <envar>PATH</envar> or move the
1215
    <filename>.dll</filename> files into the <filename>bin</filename>
1216
    directory.
1217
   </para>
1218

1219
   <para>
1220 1221
    If in doubt, refer to the manual pages of your system (perhaps
    <command>ld.so</command> or <command>rld</command>). If you later
1222 1223 1224 1225 1226 1227 1228
    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>
1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251

   <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>
1252 1253 1254 1255
  </sect2>

  <sect2>
   <title>Environment Variables</title>
1256 1257 1258 1259 1260

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

1261 1262
   <para>
    If you installed into <filename>/usr/local/pgsql</> or some other
1263
    location that is not searched for programs by default, you should
1264
    add <filename>/usr/local/pgsql/bin</> (or whatever you set
1265
    <option><literal>--bindir</></> to in <xref linkend="configure">)
1266
    into your <envar>PATH</>.  Strictly speaking, this is not
Bruce Momjian's avatar
Bruce Momjian committed
1267 1268
    necessary, but it will make the use of <productname>PostgreSQL</>
    much more convenient.
1269 1270 1271 1272 1273 1274
   </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):
1275
<programlisting>
1276
PATH=/usr/local/pgsql/bin:$PATH
1277
export PATH
1278
</programlisting>
1279
    If you are using <command>csh</> or <command>tcsh</>, then use this command:
1280
<programlisting>
Bruce Momjian's avatar
Bruce Momjian committed
1281
set path = ( /usr/local/pgsql/bin $path )
1282 1283 1284 1285
</programlisting>
   </para>

   <para>
1286 1287 1288
    <indexterm>
     <primary><envar>MANPATH</envar></primary>
    </indexterm>
1289
    To enable your system to find the <application>man</>
1290
    documentation, you need to add lines like the following to a
1291 1292
    shell start-up file unless you installed into a location that is
    searched by default.
1293
<programlisting>
1294
MANPATH=/usr/local/pgsql/man:$MANPATH
1295
export MANPATH
1296 1297 1298 1299 1300 1301 1302 1303
</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
1304 1305
    user that plans to use the database sets <envar>PGHOST</>.  This
    is not required, however: the settings can be communicated via command
1306 1307 1308 1309
    line options to most client programs.
   </para>
  </sect2>
 </sect1>
1310

1311

1312
<![%standalone-include;[
1313
 <sect1 id="install-getting-started">
1314
  <title>Getting Started</title>
1315 1316

  <para>
1317
   The following is a quick summary of how to get <productname>PostgreSQL</> up and
1318
   running once installed. The main documentation contains more information.
1319
  </para>
1320

1321 1322 1323
  <procedure>
   <step>
    <para>
1324 1325 1326 1327 1328 1329 1330
     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.
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 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379
<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
1380
kill `cat /usr/local/pgsql/data/postmaster.pid`
1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407
</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>

1408
 <sect1 id="install-whatnow">
1409 1410 1411 1412 1413 1414
  <title>What Now?</title>

  <para>
   <itemizedlist>
    <listitem>
     <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1415 1416 1417 1418 1419
      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
1420 1421 1422 1423
      changed the installation directories.
     </para>

     <para>
1424 1425 1426 1427 1428
      The first few chapters of the main documentation are the Tutorial,
      which should be your first reading if you are completely new to
      <acronym>SQL</> databases.  If you are familiar with database
      concepts then you want to proceed with part on server
      administration, which contains information about how to set up
1429
      the database server, database users, and authentication.
1430 1431 1432 1433 1434 1435 1436
     </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
1437
      suggestions for this are in the documentation.
1438 1439
     </para>
    </listitem>
1440

1441 1442
    <listitem>
     <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1443 1444 1445 1446
      Run the regression tests against the installed server (using
      <command>gmake installcheck</command>). If you didn't run the
      tests before installation, you should definitely do it now. This
      is also explained in the documentation.
1447 1448
     </para>
    </listitem>
1449

Peter Eisentraut's avatar
Peter Eisentraut committed
1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462
    <listitem>
     <para>
      By default, <productname>PostgreSQL</> is configured to run on
      minimal hardware.  This allows it to start up with almost any
      hardware configuration. The default configuration is, however,
      not designed for optimum performance. To achieve optimum
      performance, several server parameters must be adjusted, the two
      most common being <varname>shared_buffers</varname> and
      <varname> sort_mem</varname> mentioned in the documentation.
      Other parameters mentioned in the documentation also affect
      performance.
     </para>
    </listitem>
1463 1464 1465 1466 1467 1468 1469 1470 1471 1472
   </itemizedlist>
  </para>
 </sect1>
]]>


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

  <para>
1473 1474 1475 1476 1477
   <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.
1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489
  </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>
1490
     <tgroup cols="5">
1491 1492
      <thead>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1493 1494 1495 1496 1497
        <entry><acronym>OS</acronym></entry>
        <entry>Processor</entry>
        <entry>Version</entry>
        <entry>Reported</entry>
        <entry>Remarks</entry>
1498 1499 1500 1501
       </row>
      </thead>
      <tbody>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1502 1503 1504 1505 1506
        <entry><systemitem class="osname">AIX</></entry>
        <entry><systemitem>RS6000</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
          Hans-J&uuml;rgen Sch&ouml;nig (<email>hs@cybertec.at</email>)</entry>
1507
        <entry>see also <filename>doc/FAQ_AIX</filename></entry>
1508 1509
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1510 1511 1512 1513 1514
        <entry><systemitem class="osname">BSD/OS</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
1515
        <entry>4.3</entry>
1516
       </row>
1517
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1518 1519 1520 1521 1522
        <entry><systemitem class="osname">FreeBSD</></entry>
        <entry><systemitem>Alpha</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
1523
        <entry>4.8</entry>
1524
       </row>
1525
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1526 1527 1528 1529 1530
        <entry><systemitem class="osname">FreeBSD</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
1531
        <entry>4.9</entry>
1532 1533
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1534 1535 1536
        <entry><systemitem class="osname">HP-UX</></entry>
        <entry><systemitem>PA-RISC</></entry>
        <entry>7.4</entry>
1537
        <entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1538 1539
         2003-10-31, 10.20, Tom Lane (<email>tgl@sss.pgh.pa.us</email>);
         2003-11-04, 11.00, Peter Eisentraut (<email>peter_e@gmx.net</email>)
Peter Eisentraut's avatar
Peter Eisentraut committed
1540
        </entry>
1541
        <entry><command>gcc</> and <command>cc</>; see also <filename>doc/FAQ_HPUX</filename></entry>
1542
       </row>
1543
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1544 1545
        <entry><systemitem class="osname">IRIX</></entry>
        <entry><systemitem>MIPS</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1546 1547 1548 1549
        <entry>7.4</entry>
        <entry>2003-11-12,
         Robert E. Bruccoleri (<email>bruc@stone.congenomics.com</email>)</entry>
        <entry>6.5.20, <command>cc</command> only</entry>
1550
       </row>
1551
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1552 1553 1554 1555 1556 1557
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>Alpha</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
1558 1559
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1560 1561 1562 1563 1564 1565
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>arm41</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
1566
       </row>
1567
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1568 1569 1570 1571 1572 1573
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>Itanium</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
1574
       </row>
Bruce Momjian's avatar
Bruce Momjian committed
1575
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1576 1577 1578 1579 1580 1581
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>m68k</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1582
       </row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1583
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1584 1585 1586 1587 1588 1589
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>MIPS</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1590
       </row>
1591
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1592 1593 1594 1595 1596 1597
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>Opteron</></entry>
        <entry>7.4</entry>
        <entry>2003-11-01,
         Jani Averbach (<email>jaa@cc.jyu.fi</email>)</entry>
        <entry>2.6</entry>
1598
       </row>
1599
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1600 1601 1602 1603 1604 1605
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>PPC</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry></entry>
1606 1607
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1608 1609 1610 1611 1612 1613
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>S/390</></entry>
        <entry>7.4</entry>
        <entry>2003-10-25,
         No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
        <entry>2.4</entry>
1614
       </row>
1615
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1616 1617 1618 1619 1620 1621
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>Sparc</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24, 
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
        <entry>2.4, 32-bit</entry>
1622
       </row>
1623
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1624 1625 1626 1627 1628 1629
        <entry><systemitem class="osname">Linux</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
        <entry>2.4</entry>
1630
       </row>
1631
       <row>
1632
        <entry><systemitem class="osname">Mac OS X</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1633 1634 1635 1636 1637 1638
        <entry><systemitem>PPC</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         10.2.8, Adam Witney (<email>awitney@sghms.ac.uk</email>),
         10.3, Marko Karppinen (<email>marko@karppinen.fi</email>)</entry>
        <entry></entry>
1639
       </row>
1640
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1641 1642
        <entry><systemitem class="osname">NetBSD</></entry>
        <entry><systemitem>arm32</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1643 1644
        <entry>7.4</entry>
        <entry>2003-11-12,
Peter Eisentraut's avatar
Peter Eisentraut committed
1645
         Patrick Welche (<email>prlw1@newn.cam.ac.uk</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1646
        <entry>1.6ZE/acorn32</entry>
1647
       </row>
1648 1649 1650 1651 1652 1653 1654 1655
       <row>
        <entry><systemitem class="osname">NetBSD</></entry>
        <entry><systemitem>Sparc</></entry>
        <entry>7.4.1</entry>
        <entry>2003-11-26,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
        <entry>1.6.1, 32-bit</entry>
       </row>
1656
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1657 1658 1659 1660 1661 1662
        <entry><systemitem class="osname">NetBSD</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
        <entry>1.6</entry>
1663 1664
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1665 1666 1667 1668 1669
        <entry><systemitem class="osname">OpenBSD</></entry>
        <entry><systemitem>Sparc</></entry>
        <entry>7.4</entry>
        <entry>2003-11-01,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1670
        <entry>3.4</entry>
1671
       </row>
1672
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1673 1674 1675 1676 1677
        <entry><systemitem class="osname">OpenBSD</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
1678
        <entry>3.2</entry>
1679
       </row>
1680
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1681 1682 1683 1684 1685 1686
        <entry><systemitem class="osname">Solaris</></entry>
        <entry><systemitem>Sparc</></entry>
        <entry>7.4</entry>
        <entry>2003-10-26,
         Christopher Browne (<email>cbbrowne@libertyrms.info</email>)</entry>
        <entry>2.8; see also <filename>doc/FAQ_Solaris</filename></entry>
1687 1688
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1689 1690 1691 1692 1693
        <entry><systemitem class="osname">Solaris</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-26,
         Kurt Roeckx (<email>Q@ping.be</email>)</entry>
1694
        <entry>2.6; see also <filename>doc/FAQ_Solaris</filename></entry>
1695 1696
       </row>
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1697 1698 1699
        <entry><systemitem class="osname">Tru64 UNIX</></entry>
        <entry><systemitem>Alpha</></entry>
        <entry>7.4</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1700 1701
        <entry>2003-10-25, 5.1b, Peter Eisentraut (<email>peter_e@gmx.net</email>);
         2003-10-29, 4.0g, Alessio Bragadini (<email>alessio@albourne.com</email>)</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1702
        <entry></entry>
1703
       </row>
1704
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1705 1706
        <entry><systemitem class="osname">UnixWare</></entry>
        <entry><systemitem>x86</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1707 1708 1709
        <entry>7.4</entry>
        <entry>2003-11-03, Larry Rosenman (<email>ler@lerctr.org</email>)</entry>
        <entry>7.1.3; join test may fail, see also <filename>doc/FAQ_SCO</filename></entry>
1710
       </row>
1711
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1712 1713 1714 1715 1716
        <entry><systemitem class="osname">Windows with <application>Cygwin</application></></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.4</entry>
        <entry>2003-10-24,
         Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
1717
        <entry>see <filename>doc/FAQ_MSWIN</filename></entry>
1718
       </row>
1719
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1720
        <entry><systemitem class="osname">Windows</></entry>
1721
        <entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1722 1723
        <entry>7.4</entry>
        <entry>2003-10-27, 
1724 1725
         Dave Page (<email>dpage@vale-housing.co.uk</email>)</entry>
        <entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1726
         native is client-side only,
1727
<![%standalone-include[see documentation]]>
1728
<![%standalone-ignore[see <xref linkend="install-win32">]]>
1729 1730
        </entry>
       </row>
1731 1732 1733 1734 1735
      </tbody>
     </tgroup>
    </informaltable>

  <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1736
   <title>Unsupported Platforms:</title>
1737
   <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1738 1739 1740 1741
    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
1742 1743 1744 1745 1746 1747
    know that these platforms <emphasis>could</> be supported if given
    some attention.
   </para>
  </formalpara>

  <informaltable>
1748
   <tgroup cols="5">
1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759
    <thead>
     <row>
      <entry><acronym>OS</acronym></entry>
      <entry>Processor</entry>
      <entry>Version</entry>
      <entry>Reported</entry>
      <entry>Remarks</entry>
     </row>
    </thead>

    <tbody>
Bruce Momjian's avatar
Bruce Momjian committed
1760 1761 1762 1763 1764 1765 1766 1767
     <row>
      <entry><systemitem class="osname">BeOS</></entry>
      <entry><systemitem>x86</></entry>
      <entry>7.2</entry>
      <entry>2001-11-29,
       Cyril Velter (<email>cyril.velter@libertysurf.fr</email>)</entry>
      <entry>needs updates to semaphore code</entry>
     </row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1768 1769 1770 1771 1772
     <row>
      <entry><systemitem class="osname">Linux</></entry>
      <entry><systemitem>PlayStation 2</></entry>
      <entry>7.4</entry>
      <entry>2003-11-02,
Peter Eisentraut's avatar
Peter Eisentraut committed
1773
       Peter Eisentraut (<email>peter_e@gmx.net</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1774 1775
      <entry>
       needs new <filename>config.guess</filename>,
Peter Eisentraut's avatar
Peter Eisentraut committed
1776
       <option>--disable-spinlocks</option>, <literal>#undef
Peter Eisentraut's avatar
Peter Eisentraut committed
1777 1778 1779 1780 1781 1782 1783 1784 1785
       HAS_TEST_AND_SET</>, disable <function>tas_dummy()</>
      </entry>
     </row>
     <row>
      <entry><systemitem class="osname">Linux</></entry>
      <entry><systemitem>PA-RISC</></entry>
      <entry>7.4</entry>
      <entry>2003-10-25,
       No&egrave;l K&ouml;the (<email>noel@debian.org</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1786
      <entry>needs <option>--disable-spinlocks</option>, otherwise OK</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1787
     </row>
Bruce Momjian's avatar
Bruce Momjian committed
1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819
     <row>
      <entry><systemitem class="osname">NetBSD</></entry>
      <entry><systemitem>Alpha</></entry>
      <entry>7.2</entry>
      <entry>2001-11-20,
       Thomas Thai (<email>tom@minnesota.com</email>)</entry>
      <entry>1.5W</entry>
     </row>
     <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>
     <row>
      <entry><systemitem class="osname">NetBSD</></entry>
      <entry><systemitem>PPC</></entry>
      <entry>7.2</entry>
      <entry>2001-11-28,
       Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
      <entry>1.5</entry>
     </row>
     <row>
      <entry><systemitem class="osname">NetBSD</></entry>
      <entry><systemitem>VAX</></entry>
      <entry>7.1</entry>
      <entry>2001-03-30,
       Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
      <entry>1.5</entry>
     </row>
1820 1821 1822 1823 1824 1825 1826 1827 1828 1829
     <row>
      <entry><systemitem class="osname">QNX 4 RTOS</></entry>
      <entry><systemitem>x86</></entry>
      <entry>7.2</entry>
      <entry>2001-12-10,
       Bernd Tegge (<email>tegge@repas-aeg.de</email>)
      </entry>
      <entry>needs updates to semaphore code;
       see also <filename>doc/FAQ_QNX4</filename></entry>
     </row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1830
     <row>
1831
      <entry><systemitem class="osname">QNX RTOS v6</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1832 1833 1834
      <entry><systemitem>x86</></entry>
      <entry>7.2</entry>
      <entry>2001-11-20, Igor Kovalenko (<email>Igor.Kovalenko@motorola.com</email>)</entry>
1835
      <entry>patches available in archives, but too late for 7.2</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1836
     </row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1837 1838 1839 1840 1841 1842 1843 1844
     <row>
      <entry><systemitem class="osname">SCO OpenServer</></entry>
      <entry><systemitem>x86</></entry>
      <entry>7.3.1</entry>
      <entry>2002-12-11, 
       Shibashish Satpathy (<email>shib@postmark.net</>)</entry>
      <entry>5.0.4, <command>gcc</>;  see also <filename>doc/FAQ_SCO</filename></entry>
     </row>
Bruce Momjian's avatar
Bruce Momjian committed
1845 1846 1847 1848 1849 1850 1851
     <row>
      <entry><systemitem class="osname">SunOS 4</></entry>
      <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>
1852 1853 1854 1855 1856 1857
    </tbody>
   </tgroup>
  </informaltable>
 </sect1>

</chapter>
1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875

<!-- 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:
-->