installation.sgml 65.7 KB
Newer Older
Bruce Momjian's avatar
Bruce Momjian committed
1
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.135 2003/06/15 04:07:58 momjian 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 172 173 174
     </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.
175
      Since PL/Python will be a shared library, the
176 177 178
      <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
179 180 181 182 183 184 185 186
      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:
187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202
<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
203 204
      the <productname>PostgreSQL</> build system of this.  Consult
      the <filename>Makefile</filename> in the
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 254
      <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
255 256 257 258 259 260
      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
261
      url="http://www.postgresql.org/~petere/gettext.html" ></ulink>.
262
      If you are using the <application>Gettext</> implementation in
Bruce Momjian's avatar
Bruce Momjian committed
263 264 265 266
      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.
267 268 269 270 271
     </para>
    </listitem>

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

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

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

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

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

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

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

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

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

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

359 360
  <para>
   The internal data storage format changes with new releases of
361 362
   <productname>PostgreSQL</>. Therefore, if you are upgrading an
   existing installation that does not have a version number
363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383
   <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>
384 385 386 387
     <indexterm>
      <primary>pg_dumpall</primary>
     </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 409 410 411 412 413 414 415
     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>
     command from PostgreSQL &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.
416 417
    </para>
   </step>
418

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

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

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


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

  <procedure>

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

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

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

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

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

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

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

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

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

      <varlistentry>
613
       <term><option>--docdir=<replaceable>DIRECTORY</></option></term>
614 615 616 617 618 619 620 621 622 623
       <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>
624
       <term><option>--mandir=<replaceable>DIRECTORY</></option></term>
625 626 627 628 629
       <listitem>
        <para>
         The man pages that come with <productname>PostgreSQL</> will be installed under
         this directory, in their respective
         <filename>man<replaceable>x</></> subdirectories.
630
         The default is <filename><replaceable>PREFIX</>/man</>.
631 632 633
        </para>
       </listitem>
      </varlistentry>
634 635 636 637
     </variablelist>

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

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

      <varlistentry>
687
       <term><option>--with-libraries=<replaceable>DIRECTORIES</></option></term>
688 689 690 691 692 693 694 695 696 697 698 699 700 701 702
       <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>
703
       <term><option>--enable-recode</option></term>
704 705
       <listitem>
        <para>
706
         Enables single-byte character set recode support. See
707
         <![%standalone-include[the documentation]]> <![%standalone-ignore[<xref
708 709 710
         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
711
        </para>
712 713 714
       </listitem>
      </varlistentry>

715
      <varlistentry>
716
       <term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term>
717 718
       <listitem>
        <para>
719 720 721 722 723 724 725 726 727 728
         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.
729 730 731 732
        </para>

        <para>
         To use this option, you will need an implementation of the
733
         <application>Gettext</> API; see above.
734 735 736 737
        </para>
       </listitem>
      </varlistentry>

738
      <varlistentry>
739
       <term><option>--with-pgport=<replaceable>NUMBER</></option></term>
740 741 742 743 744 745
       <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,
746 747 748
         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.
749 750 751 752 753
        </para>
       </listitem>
      </varlistentry>

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

      <varlistentry>
763
       <term><option>--with-python</option></term>
764 765
       <listitem>
        <para>
766 767 768
         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
769 770 771 772 773 774
         (<filename>/usr/lib/python<replaceable>x</>.<replaceable>y</></>).
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
775
       <term><option>--with-tcl</option></term>
776 777
       <listitem>
        <para>
778
         Build components that require Tcl/Tk, which are
779
         <application>libpgtcl</>, <application>pgtclsh</>,
780
         <application>pgtksh</application>,
781
         and <application>PL/Tcl</>.  But see below about
782
         <option>--without-tk</>.
783 784 785 786 787
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
788
       <term><option>--without-tk</option></term>
789 790
       <listitem>
        <para>
791
         If you specify <option>--with-tcl</> and this option, then
792 793
         the program that requires <productname>Tk</>
         (<application>pgtksh</>) will be
794
         excluded.
795 796 797 798 799
        </para>
       </listitem>
      </varlistentry>

      <varlistentry>
800 801
       <term><option>--with-tclconfig=<replaceable>DIRECTORY</replaceable></option></term>
       <term><option>--with-tkconfig=<replaceable>DIRECTORY</replaceable></option></term>
802 803 804
       <listitem>
        <para>
         Tcl/Tk installs the files <filename>tclConfig.sh</filename> and
805 806
         <filename>tkConfig.sh</filename>, which contain
         configuration information needed to build modules
807
         interfacing to Tcl or Tk. These files are normally found
808
         automatically at their well-known locations, but if you want to
809
         use a different version of Tcl or Tk you can specify the
810
         directory in which to find them.
811 812 813 814
        </para>
       </listitem>
      </varlistentry>

815 816 817 818 819
      <varlistentry>
       <term><option>--with-java</option></term>
       <listitem>
        <para>
         Build the <acronym>JDBC</acronym> driver and associated Java
820
         packages.
821 822 823 824
        </para>
       </listitem>
      </varlistentry>

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

863
      <varlistentry>
864 865 866 867 868
       <indexterm>
        <primary>OpenSSL</primary>
        <seealso>SSL</seealso>
       </indexterm>

Peter Eisentraut's avatar
Peter Eisentraut committed
869
       <term><option>--with-openssl<optional>=<replaceable>DIRECTORY</></></option></term>
870 871
       <listitem>
        <para>
872 873
         Build with support for <acronym>SSL</> (encrypted) connections. 
         This requires the <productname>OpenSSL</> package to be installed.
874
         The <replaceable>DIRECTORY</> argument specifies the
875 876
         root directory of the <productname>OpenSSL</> installation; the
         default is <filename>/usr/local/ssl</>.
877 878 879 880
        </para>

        <para>
         <filename>configure</> will check for the required header
881
         files and libraries to make sure that your <productname>OpenSSL</>
882 883 884 885 886
         installation is sufficient before proceeding.
        </para>
       </listitem>
      </varlistentry>

Peter Eisentraut's avatar
Peter Eisentraut committed
887
      <varlistentry>
888
       <term><option>--with-pam</option></term>
Peter Eisentraut's avatar
Peter Eisentraut committed
889 890
       <listitem>
        <para>
891 892
	 Build with <acronym>PAM</> (Pluggable Authentication Modules)
	 support.
Peter Eisentraut's avatar
Peter Eisentraut committed
893 894 895 896
        </para>
       </listitem>
      </varlistentry>

897 898 899 900
      <varlistentry>
       <term><option>--without-readline</option></term>
       <listitem>
        <para>
901
         Prevents the use of the <application>Readline</> library.  This disables
902 903 904 905 906 907
         command-line editing and history in
         <application>psql</application>, so it is not recommended.
        </para>
       </listitem>
      </varlistentry>

908 909 910 911 912 913 914 915 916
      <varlistentry>
       <term><option>--with-rendezvous</option></term>
       <listitem>
        <para>
	 Build with Rendezvous support.
        </para>
       </listitem>
      </varlistentry>

917 918 919 920
      <varlistentry>
       <term><option>--with-threads</option></term>
       <listitem>
        <para>
Bruce Momjian's avatar
Bruce Momjian committed
921 922
	 Allow separate libpq and ecpg threads to safely control their
         private connection handles.
923 924 925 926
        </para>
       </listitem>
      </varlistentry>

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

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

      <varlistentry>
958
       <term><option>--enable-cassert</option></term>
Tom Lane's avatar
Tom Lane committed
959 960 961 962 963 964 965 966
       <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
967
	 still lead to server restarts if it triggers an assertion
Tom Lane's avatar
Tom Lane committed
968 969 970
	 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.
971 972 973
        </para>
       </listitem>
      </varlistentry>
974 975 976 977 978 979 980 981 982 983 984 985 986 987 988

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

989
     </variablelist>
990
    </para>
991

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

  <step>
   <title>Build</title>

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

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

1031 1032 1033 1034
   <indexterm>
    <primary>regression test</primary>
   </indexterm>

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

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

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

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

1094
   <para>
1095
    If you built the Python interfaces and you were not the
1096 1097 1098 1099 1100 1101
    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>
1102
    If you do not have root access you are on your own: 
1103 1104 1105
    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.
1106 1107
   </para>

1108
   <para>
1109
    The standard installation provides only the header files needed for client
1110
    application development.  If you plan to do any server-side program
1111
    development (such as custom functions or data types written in C),
1112 1113 1114 1115 1116
    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
1117
    This adds a megabyte or two to the installation footprint, and is only
1118 1119 1120 1121 1122
    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>

1123
   <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1124
    <title>Client-only installation:</title>
1125 1126
    <para>
     If you want to install only the client applications and
1127
     interface libraries, then you can use these commands:
1128 1129
<screen>
<userinput>gmake -C src/bin install</>
1130
<userinput>gmake -C src/include install</>
1131 1132 1133 1134 1135
<userinput>gmake -C src/interfaces install</>
<userinput>gmake -C doc install</>
</screen>
    </para>
   </formalpara>
1136 1137
  </step>
  </procedure>
1138

1139
  <formalpara>
1140
   <title>Uninstallation:</title>
1141 1142
   <para>
    To undo the installation use the command <command>gmake
1143
    uninstall</>. However, this will not remove any created directories.
1144
   </para>
1145
  </formalpara>
1146

1147 1148 1149 1150 1151 1152
  <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
1153
    clean</>. This will preserve the files made by the <command>configure</command>
1154 1155 1156 1157 1158 1159 1160
    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>
1161

1162
  <para>
1163 1164
   If you perform a build and then discover that your <command>configure</>
   options were wrong, or if you change anything that <command>configure</>
1165 1166 1167
   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
1168 1169
   may not propagate everywhere they need to.
  </para>
1170 1171
 </sect1>

1172
 <sect1 id="install-post">
1173 1174 1175 1176
  <title>Post-Installation Setup</title>

  <sect2>
   <title>Shared Libraries</title>
1177 1178 1179 1180 1181

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

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

1218
   <para>
1219
    On some systems it might be preferable to set the environment
1220 1221 1222 1223
    variable <envar>LD_RUN_PATH</envar> <emphasis>before</emphasis>
    building.
   </para>

1224
   <para>
1225
    On <systemitem class="osname">Cygwin</systemitem>, put the library
1226
    directory in the <envar>PATH</envar> or move the
1227
    <filename>.dll</filename> files into the <filename>bin</filename>
1228
    directory.
1229
   </para>
1230

1231
   <para>
1232 1233
    If in doubt, refer to the manual pages of your system (perhaps
    <command>ld.so</command> or <command>rld</command>). If you later
1234 1235 1236 1237 1238 1239 1240
    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>
1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263

   <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>
1264 1265 1266 1267
  </sect2>

  <sect2>
   <title>Environment Variables</title>
1268 1269 1270 1271 1272

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

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

   <para>
1298 1299 1300 1301
    <indexterm>
     <primary><envar>MANPATH</envar></primary>
     <seealso>man pages</seealso>
    </indexterm>
1302
    To enable your system to find the <application>man</>
1303
    documentation, you need to add lines like the following to a
1304 1305
    shell start-up file unless you installed into a location that is
    searched by default.
1306
<programlisting>
1307
MANPATH=/usr/local/pgsql/man:$MANPATH
1308
export MANPATH
1309 1310 1311 1312 1313 1314 1315 1316
</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
1317 1318
    user that plans to use the database sets <envar>PGHOST</>.  This
    is not required, however: the settings can be communicated via command
1319 1320 1321 1322
    line options to most client programs.
   </para>
  </sect2>
 </sect1>
1323

1324

1325
<![%standalone-include;[
1326
 <sect1 id="install-getting-started">
1327
  <title>Getting Started</title>
1328 1329

  <para>
1330
   The following is a quick summary of how to get <productname>PostgreSQL</> up and
1331
   running once installed. The main documentation contains more information.
1332
  </para>
1333

1334 1335 1336
  <procedure>
   <step>
    <para>
1337 1338 1339 1340 1341 1342 1343
     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.
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 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392
<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
1393
kill `cat /usr/local/pgsql/data/postmaster.pid`
1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420
</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>

1421
 <sect1 id="install-whatnow">
1422 1423 1424 1425 1426 1427
  <title>What Now?</title>

  <para>
   <itemizedlist>
    <listitem>
     <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1428 1429 1430 1431 1432
      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
1433 1434 1435 1436
      changed the installation directories.
     </para>

     <para>
1437 1438 1439 1440 1441
      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
1442
      the database server, database users, and authentication.
1443 1444 1445 1446 1447 1448 1449
     </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
1450
      suggestions for this are in the documentation.
1451 1452
     </para>
    </listitem>
1453

1454 1455 1456 1457 1458
    <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
1459
      explained in the documentation.
1460 1461
     </para>
    </listitem>
1462

1463 1464 1465 1466
   </itemizedlist>
  </para>

<!-- do we still ship this? -->
1467
<!--
1468 1469 1470
  <para>
   The documentation is also available in Postscript format. If you
   have a Postscript printer, or have your machine already set up to
1471 1472
   accept Postscript files using a print filter, then to print, the
   documentation simply type
1473 1474
<programlisting>
cd /usr/local/pgsql/doc
1475
gunzip -c postgres.ps.gz | lpr
1476 1477 1478 1479
</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>
1480
gunzip -c postgres.ps.gz \
1481 1482 1483 1484 1485 1486
    | 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>
1487 1488
-->

1489 1490 1491 1492 1493 1494 1495 1496
 </sect1>
]]>


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

  <para>
1497 1498 1499 1500 1501
   <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.
1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513
  </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>
1514
     <tgroup cols="5">
1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525
      <thead>
       <row>
	<entry><acronym>OS</acronym></entry>
	<entry>Processor</entry>
	<entry>Version</entry>
	<entry>Reported</entry>
	<entry>Remarks</entry>
       </row>
      </thead>
      <tbody>
       <row>
1526
	<entry><systemitem class="osname">AIX</></entry>
1527
	<entry><systemitem>RS6000</></entry>
1528 1529
	<entry>7.3</entry>
	<entry>2002-11-12,
Peter Eisentraut's avatar
Peter Eisentraut committed
1530
	 Andreas Zeugswetter (<email>ZeugswetterA@spardat.at</email>)</entry>
1531
        <entry>see also <filename>doc/FAQ_AIX</filename></entry>
1532 1533
       </row>
       <row>
1534
	<entry><systemitem class="osname">BSD/OS</></entry>
1535
	<entry><systemitem>x86</></entry>
1536 1537
	<entry>7.3</entry>
	<entry>2002-10-25,
1538 1539
	 Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
        <entry>4.2</entry>
1540
       </row>
1541 1542 1543
       <row>
	<entry><systemitem class="osname">FreeBSD</></entry>
	<entry><systemitem>Alpha</></entry>
1544
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1545
	<entry>2002-11-13,
1546 1547 1548
	 Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
        <entry></entry>
       </row>
1549
       <row>
1550
	<entry><systemitem class="osname">FreeBSD</></entry>
1551
	<entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1552
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1553
	<entry>2002-10-29,
Bruce Momjian's avatar
Bruce Momjian committed
1554
	 3.3, Nigel J. Andrews (<email>nandrews@investsystems.co.uk</email>),
Tom Lane's avatar
Tom Lane committed
1555
	 4.7, Larry Rosenman (<email>ler@lerctr.org</email>),
Bruce Momjian's avatar
Bruce Momjian committed
1556
	 5.0, Sean Chittenden (<email>sean@chittenden.org</email>)</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1557
        <entry></entry>
1558 1559
       </row>
       <row>
1560 1561
	<entry><systemitem class="osname">HP-UX</></entry>
	<entry><systemitem>PA-RISC</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1562
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1563
        <entry>2002-10-28,
1564
	 10.20 Tom Lane (<email>tgl@sss.pgh.pa.us</email>),
1565 1566
	 11.00, 11.11, 32 and 64 bit, Giles Lean (<email>giles@nemeton.com.au</email>)</entry>
        <entry><command>gcc</> and <command>cc</>; see also <filename>doc/FAQ_HPUX</filename></entry>
1567
       </row>
1568
       <row>
1569
	<entry><systemitem class="osname">IRIX</></entry>
1570
	<entry><systemitem>MIPS</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1571 1572 1573 1574
	<entry>7.3</entry>
	<entry>2002-10-27,
	 Ian Barwick (<email>barwick@gmx.net</email>)</entry>
	<entry>Irix64 Komma 6.5</entry>
1575 1576
       </row>
       <row>
1577
	<entry><systemitem class="osname">Linux</></entry>
1578
	<entry><systemitem>Alpha</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1579
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1580
	<entry>2002-10-28,
Bruce Momjian's avatar
Bruce Momjian committed
1581
	 Magnus Naeslund (<email>mag@fbab.net</email>)</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1582
	<entry>2.4.19-pre6</entry>
1583 1584
       </row>
       <row>
1585
	<entry><systemitem class="osname">Linux</></entry>
1586
	<entry><systemitem>armv4l</></entry>
1587 1588 1589
	<entry>7.2</entry>
	<entry>2001-12-10,
	 Mark Knox (<email>segfault@hardline.org</email>)</entry>
1590
	<entry>2.2.x</entry>
1591 1592
       </row>
       <row>
1593
	<entry><systemitem class="osname">Linux</></entry>
1594
	<entry><systemitem>MIPS</></entry>
1595
	<entry>7.2</entry>
1596 1597 1598
	<entry>2001-11-15,
	 Hisao Shibuya (<email>shibuya@alpha.or.jp</>)</entry>
	<entry>2.0.x; <productname>Cobalt Qube2</></entry>
1599
       </row>
1600 1601
       <row>
	<entry><systemitem class="osname">Linux</></entry>
1602
	<entry><systemitem>PlayStation 2</></entry>
1603 1604
	<entry>7.3</entry>
	<entry>2002-11-19,
1605
	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
1606
	<entry><literal>#undef HAS_TEST_AND_SET</>, remove <type>slock_t</> <literal>typedef</></entry>
1607
       </row>
1608
       <row>
1609
	<entry><systemitem class="osname">Linux</></entry>
1610
	<entry><systemitem>PPC74xx</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1611 1612
	<entry>7.3</entry>
	<entry>2002-10-26,
1613
	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1614 1615
	<entry>bye
	2.2.18; Apple G3</entry>
1616 1617
       </row>
       <row>
1618 1619
	<entry><systemitem class="osname">Linux</></entry>
	<entry><systemitem>S/390</></entry>
1620 1621
	<entry>7.3</entry>
	<entry>2002-11-22,
1622
	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
1623
	<entry>both s390 and s390x (32 and 64 bit)</entry>
1624
       </row>
1625
       <row>
1626
	<entry><systemitem class="osname">Linux</></entry>
1627
	<entry><systemitem>Sparc</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1628 1629 1630 1631
	<entry>7.3</entry>
	<entry>2002-10-26, 
	 Doug McNaught (<email>doug@mcnaught.org</email>)</entry>
	<entry>3.0</entry>
1632
       </row>
1633
       <row>
1634 1635
	<entry><systemitem class="osname">Linux</></entry>
	<entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1636 1637 1638 1639
	<entry>7.3</entry>
	<entry>2002-10-26,
	 Alvaro Herrera (<email>alvherre@dcc.uchile.cl</email>)</entry>
	<entry>2.4</entry>
1640
       </row>
1641
       <row>
1642 1643
	<entry><systemitem class="osname">MacOS X</></entry>
	<entry><systemitem>PPC</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1644
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1645
	<entry>2002-10-28,
1646
	 10.1, Tom Lane (<email>tgl@sss.pgh.pa.us</email>),
Bruce Momjian's avatar
Bruce Momjian committed
1647 1648
	 10.2.1, Adam Witney (<email>awitney@sghms.ac.uk</email>)</entry>
	<entry></entry>
1649
       </row>
1650
       <row>
1651
	<entry><systemitem class="osname">NetBSD</></entry>
1652
	<entry><systemitem>Alpha</></entry>
1653
	<entry>7.2</entry>
1654 1655 1656
	<entry>2001-11-20,
	 Thomas Thai (<email>tom@minnesota.com</email>)</entry>
	<entry>1.5W</entry>
1657 1658
       </row>
       <row>
1659
	<entry><systemitem class="osname">NetBSD</></entry>
1660
	<entry><systemitem>arm32</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1661 1662 1663 1664
	<entry>7.3</entry>
	<entry>2002-11-19,
	 Patrick Welche (<email>prlw1@newn.cam.ac.uk</email>)</entry>
	<entry>1.6</entry>
1665
       </row>
1666
       <row>
1667 1668
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>m68k</></entry>
1669
	<entry>7.0</entry>
1670 1671
	<entry>2000-04-10,
	 Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
1672 1673
	<entry>Mac 8xx</entry>
       </row>
1674 1675 1676 1677 1678 1679 1680 1681
      <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>
1682
       <row>
1683 1684
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>PPC</></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
       </row>
1690
       <row>
1691 1692
	<entry><systemitem class="osname">NetBSD</></entry>
	<entry><systemitem>Sparc</></entry>
1693 1694 1695
	<entry>7.2</entry>
	<entry>2001-12-03,
	 Matthew Green (<email>mrg@eterna.com.au</email>)</entry>
1696
	<entry>32- and 64-bit builds</entry>
1697
       </row>
1698
       <row>
1699
        <entry><systemitem class="osname">NetBSD</></entry>
1700
        <entry><systemitem>VAX</></entry>
1701
        <entry>7.1</entry>
1702 1703 1704
        <entry>2001-03-30,
	 Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
        <entry>1.5</entry>
1705 1706
       </row>
       <row>
1707
	<entry><systemitem class="osname">NetBSD</></entry>
1708
	<entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1709 1710 1711 1712
	<entry>7.3</entry>
	<entry>2002-11-14,
	 Patrick Welche (<email>prlw1@newn.cam.ac.uk</email>)</entry>
	<entry>1.6</entry>
1713 1714
       </row>
       <row>
1715
	<entry><systemitem class="osname">OpenBSD</></entry>
1716
	<entry><systemitem>Sparc</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1717 1718 1719 1720
	<entry>7.3</entry>
	<entry>2002-11-17,
	 Christopher Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
        <entry>3.2</entry>
1721
       </row>
1722
       <row>
1723
	<entry><systemitem class="osname">OpenBSD</></entry>
1724
	<entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1725 1726
	<entry>7.3</entry>
	<entry>2002-11-14,
1727
	 3.1 Magnus Naeslund (<email>mag@fbab.net</email>),
Bruce Momjian's avatar
Bruce Momjian committed
1728 1729
	 3.2 Christopher Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
        <entry></entry>
1730
       </row>
1731 1732 1733 1734 1735
       <row>
        <entry><systemitem class="osname">SCO OpenServer 5</></entry>
        <entry><systemitem>x86</></entry>
        <entry>7.3.1</entry>
        <entry>2002-12-11, Shibashish Satpathy (<email>shib@postmark.net</>)</entry>
1736
        <entry>5.0.4, <command>gcc</>;  see also <filename>doc/FAQ_SCO</filename></entry>
1737
       </row>
1738
       <row>
1739
	<entry><systemitem class="osname">Solaris</></entry>
1740
	<entry><systemitem>Sparc</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1741
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1742 1743
	<entry>2002-10-28,
	 Andrew Sullivan (<email>andrew@libertyrms.info</email>)</entry>
1744
	<entry>Solaris 7 and 8; see also <filename>doc/FAQ_Solaris</filename></entry>
1745 1746
       </row>
       <row>
1747
	<entry><systemitem class="osname">Solaris</></entry>
1748
	<entry><systemitem>x86</></entry>
1749 1750
	<entry>7.3</entry>
	<entry>2002-11-20,
1751
	 Martin Renters (<email>martin@datafax.com</email>)</entry>
1752
	<entry>5.8; see also <filename>doc/FAQ_Solaris</filename></entry>
1753
       </row>
Bruce Momjian's avatar
Bruce Momjian committed
1754 1755 1756 1757 1758 1759 1760
       <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>
1761
       <row>
Peter Eisentraut's avatar
Peter Eisentraut committed
1762
	<entry><systemitem class="osname">Tru64 UNIX</></entry>
1763
	<entry><systemitem>Alpha</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1764 1765 1766 1767
	<entry>7.3</entry>
	<entry>2002-11-05,
	 Alessio Bragadini (<email>alessio@albourne.com</email>)</entry>
        <entry></entry>
1768
       </row>
1769 1770 1771 1772
       <row>
	<entry><systemitem class="osname">UnixWare</></entry>
	<entry><systemitem>x86</></entry>
	<entry>7.3</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1773 1774
	<entry>2002-11-01,
	 7.1.3 Larry Rosenman (<email>ler@lerctr.org</email>),
1775
	 7.1.1 and 7.1.2(8.0.0) Olivier Prenant (<email>ohp@pyrenet.fr</email>)</entry>
Bruce Momjian's avatar
Bruce Momjian committed
1776
	<entry>see also <filename>doc/FAQ_SCO</filename></entry>
1777
       </row>
1778
       <row>
1779
	<entry><systemitem class="osname">Windows</></entry>
1780
	<entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1781 1782
	<entry>7.3</entry>
	<entry>2002-10-29,
1783
	 Dave Page (<email>dpage@vale-housing.co.uk</email>),
1784
	 Jason Tishler (<email>jason@tishler.net</email>)</entry>
1785
        <entry>with <application>Cygwin</application>; see <filename>doc/FAQ_MSWIN</filename></entry>
1786
       </row>
1787 1788 1789
      <row>
       <entry><systemitem class="osname">Windows</></entry>
       <entry><systemitem>x86</></entry>
Bruce Momjian's avatar
Bruce Momjian committed
1790 1791
       <entry>7.3</entry>
       <entry>2002-11-05,
1792 1793 1794
	Dave Page (<email>dpage@vale-housing.co.uk</email>)</entry>
       <entry>
	native is client-side only;
1795
<![%standalone-include[see documentation]]>
1796 1797 1798
<![%standalone-ignore[see <xref linkend="install-win32">]]>
       </entry>
      </row>
1799 1800 1801 1802 1803
      </tbody>
     </tgroup>
    </informaltable>

  <formalpara>
Peter Eisentraut's avatar
Peter Eisentraut committed
1804
   <title>Unsupported Platforms:</title>
1805
   <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
1806 1807 1808 1809
    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
1810 1811 1812 1813 1814 1815
    know that these platforms <emphasis>could</> be supported if given
    some attention.
   </para>
  </formalpara>

  <informaltable>
1816
   <tgroup cols="5">
1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827
    <thead>
     <row>
      <entry><acronym>OS</acronym></entry>
      <entry>Processor</entry>
      <entry>Version</entry>
      <entry>Reported</entry>
      <entry>Remarks</entry>
     </row>
    </thead>

    <tbody>
1828 1829 1830 1831 1832 1833
       <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>
1834
	<entry>needs updates to semaphore code</entry>
1835
       </row>
1836
     <row>
1837
      <entry><systemitem class="osname">DG/UX 5.4R4.11</></entry>
1838
      <entry><systemitem>m88k</></entry>
1839
      <entry>6.3</entry>
1840
      <entry>1998-03-01, Brian E Gallew (<email>geek+@cmu.edu</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1841
      <entry>no recent reports</entry>
1842
     </row>
1843
     <row>
1844 1845
      <entry><systemitem class="osname">MkLinux DR1</></entry>
      <entry><systemitem>PPC750</></entry>
1846 1847 1848 1849
      <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>
1850
     <row>
1851
      <entry><systemitem class="osname">NeXTSTEP</></entry>
1852
      <entry><systemitem>x86</></entry>
1853 1854
      <entry>6.x</entry>
      <entry>1998-03-01, David Wetzel (<email>dave@turbocat.de</email>)</entry>
1855
      <entry>bit rot suspected</entry>
1856
     </row>
1857 1858 1859 1860 1861 1862 1863 1864 1865 1866
     <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
1867
     <row>
1868
      <entry><systemitem class="osname">QNX RTOS v6</></entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1869 1870 1871
      <entry><systemitem>x86</></entry>
      <entry>7.2</entry>
      <entry>2001-11-20, Igor Kovalenko (<email>Igor.Kovalenko@motorola.com</email>)</entry>
1872
      <entry>patches available in archives, but too late for 7.2</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1873
     </row>
1874
     <row>
1875 1876
      <entry><systemitem class="osname">System V R4</></entry>
      <entry><systemitem>m88k</></entry>
1877
      <entry>6.2.1</entry>
1878
      <entry>1998-03-01, Doug Winterburn (<email>dlw@seavme.xroads.com</email>)</entry>
1879
      <entry>needs new <acronym>TAS</acronym> spinlock code</entry>
1880 1881
     </row>
     <row>
1882 1883
      <entry><systemitem class="osname">System V R4</></entry>
      <entry><systemitem>MIPS</></entry>
1884
      <entry>6.4</entry>
1885
      <entry>1998-10-28, Frank Ridderbusch (<email>ridderbusch.pad@sni.de</email>)</entry>
Peter Eisentraut's avatar
Peter Eisentraut committed
1886
      <entry>no recent reports</entry>
1887 1888
     </row>
     <row>
1889 1890
      <entry><systemitem class="osname">Ultrix</></entry>
      <entry><systemitem>MIPS</></entry>
1891 1892
      <entry>7.1</entry>
      <entry>2001-03-26</entry>
1893
      <entry><acronym>TAS</acronym> spinlock code not detected</entry>
1894 1895
     </row>
     <row>
1896 1897
      <entry><systemitem class="osname">Ultrix</></entry>
      <entry><systemitem>VAX</></entry>
1898
      <entry>6.x</entry>
1899
      <entry>1998-03-01</entry>
1900
      <entry></entry>
1901
     </row>
1902 1903 1904 1905 1906 1907
    </tbody>
   </tgroup>
  </informaltable>
 </sect1>

</chapter>
1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925

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