+ linkend="migration">,]]> which you are encouraged to read in any
+ case.
+
+
+
+
+
+ Installation Procedure
+
+
+
+
+ Configuration</></div>
<div class="diff add">+</div>
<div class="diff add">+ <indexterm zone="configure"></div>
<div class="diff add">+ <primary>configure</primary></div>
<div class="diff add">+ </indexterm></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The first step of the installation procedure is to configure the</div>
<div class="diff add">+ source tree for your system and choose the options you would like.</div>
<div class="diff add">+ This is done by running the <filename>configure</> script. For a</div>
<div class="diff add">+ default installation simply enter</div>
<div class="diff add">+<screen></div>
<div class="diff add">+<userinput>./configure</userinput></div>
<div class="diff add">+</screen></div>
<div class="diff add">+ This script will run a number of tests to guess values for various</div>
<div class="diff add">+ system dependent variables and detect some quirks of your</div>
<div class="diff add">+ operating system, and finally will create several files in the</div>
<div class="diff add">+ build tree to record what it found. (You can also run</div>
<div class="diff add">+ <filename>configure</filename> in a directory outside the source</div>
<div class="diff add">+ tree if you want to keep the build directory separate.)</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The default configuration will build the server and utilities, as</div>
<div class="diff add">+ well as all client applications and interfaces that require only a</div>
<div class="diff add">+ C compiler. All files will be installed under</div>
<div class="diff add">+ <filename>/usr/local/pgsql</> by default.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ You can customize the build and installation process by supplying one</div>
<div class="diff add">+ or more of the following command line options to</div>
<div class="diff add">+ <filename>configure</filename>:</div>
<div class="diff add">+</div>
<div class="diff add">+ <variablelist></div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--prefix=<replaceable>PREFIX</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Install all files under the directory <replaceable>PREFIX</></div>
<div class="diff add">+ instead of <filename>/usr/local/pgsql</filename>. The actual</div>
<div class="diff add">+ files will be installed into various subdirectories; no files</div>
<div class="diff add">+ will ever be installed directly into the</div>
<div class="diff add">+ <replaceable>PREFIX</> directory.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ If you have special needs, you can also customize the</div>
<div class="diff add">+ individual subdirectories with the following options. However,</div>
<div class="diff add">+ if you leave these with their defaults, the installation will be</div>
<div class="diff add">+ relocatable, meaning you can move the directory after</div>
<div class="diff add">+ installation. (The <literal>man</> and <literal>doc</></div>
<div class="diff add">+ locations are not affected by this.)</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ For relocatable installs, you might want to use </div>
<div class="diff add">+ <filename>configure</filename>'s <literal>--disable-rpath</></div>
<div class="diff add">+ option. Also, you will need to tell the operating system how</div>
<div class="diff add">+ to find the shared libraries.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--exec-prefix=<replaceable>EXEC-PREFIX</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ You can install architecture-dependent files under a</div>
<div class="diff add">+ different prefix, <replaceable>EXEC-PREFIX</>, than what</div>
<div class="diff add">+ <replaceable>PREFIX</> was set to. This can be useful to</div>
<div class="diff add">+ share architecture-independent files between hosts. If you</div>
<div class="diff add">+ omit this, then <replaceable>EXEC-PREFIX</> is set equal to</div>
<div class="diff add">+ <replaceable>PREFIX</> and both architecture-dependent and</div>
<div class="diff add">+ independent files will be installed under the same tree,</div>
<div class="diff add">+ which is probably what you want.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--bindir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Specifies the directory for executable programs. The default</div>
<div class="diff add">+ is <filename><replaceable>EXEC-PREFIX</>/bin</>, which</div>
<div class="diff add">+ normally means <filename>/usr/local/pgsql/bin</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--datadir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Sets the directory for read-only data files used by the</div>
<div class="diff add">+ installed programs. The default is</div>
<div class="diff add">+ <filename><replaceable>PREFIX</>/share</>. Note that this has</div>
<div class="diff add">+ nothing to do with where your database files will be placed.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--sysconfdir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The directory for various configuration files,</div>
<div class="diff add">+ <filename><replaceable>PREFIX</>/etc</> by default.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--libdir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The location to install libraries and dynamically loadable</div>
<div class="diff add">+ modules. The default is</div>
<div class="diff add">+ <filename><replaceable>EXEC-PREFIX</>/lib</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--includedir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The directory for installing C and C++ header files. The</div>
<div class="diff add">+ default is <filename><replaceable>PREFIX</>/include</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--mandir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The man pages that come with <productname>PostgreSQL</> will be installed under</div>
<div class="diff add">+ this directory, in their respective</div>
<div class="diff add">+ <filename>man<replaceable>x</></> subdirectories.</div>
<div class="diff add">+ The default is <filename><replaceable>PREFIX</>/man</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-docdir=<replaceable>DIRECTORY</></option></term></div>
<div class="diff add">+ <term><option>--without-docdir</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Documentation files, except <quote>man</> pages, will be</div>
<div class="diff add">+ installed into this directory. The default is</div>
<div class="diff add">+ <filename><replaceable>PREFIX</>/doc</>. If the option</div>
<div class="diff add">+ <option>--without-docdir</option> is specified, the</div>
<div class="diff add">+ documentation will not be installed by <command>make</div>
<div class="diff add">+ install</command>. This is intended for packaging scripts</div>
<div class="diff add">+ that have special methods for installing documentation.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+ </variablelist></div>
<div class="diff add">+</div>
<div class="diff add">+ <note></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Care has been taken to make it possible to install</div>
<div class="diff add">+ <productname>PostgreSQL</> into shared installation locations</div>
<div class="diff add">+ (such as <filename>/usr/local/include</filename>) without</div>
<div class="diff add">+ interfering with the namespace of the rest of the system. First,</div>
<div class="diff add">+ the string <quote><literal>/postgresql</literal></quote> is</div>
<div class="diff add">+ automatically appended to <varname>datadir</varname>,</div>
<div class="diff add">+ <varname>sysconfdir</varname>, and <varname>docdir</varname>,</div>
<div class="diff add">+ unless the fully expanded directory name already contains the</div>
<div class="diff add">+ string <quote><literal>postgres</></quote> or</div>
<div class="diff add">+ <quote><literal>pgsql</></quote>. For example, if you choose</div>
<div class="diff add">+ <filename>/usr/local</filename> as prefix, the documentation will</div>
<div class="diff add">+ be installed in <filename>/usr/local/doc/postgresql</filename>,</div>
<div class="diff add">+ but if the prefix is <filename>/opt/postgres</filename>, then it</div>
<div class="diff add">+ will be in <filename>/opt/postgres/doc</filename>. The public C</div>
<div class="diff add">+ header files of the client interfaces are installed into</div>
<div class="diff add">+ <varname>includedir</varname> and are namespace-clean. The</div>
<div class="diff add">+ internal header files and the server header files are installed</div>
<div class="diff add">+ into private directories under <varname>includedir</varname>. See</div>
<div class="diff add">+ the documentation of each interface for information about how to</div>
<div class="diff add">+ get at the its header files. Finally, a private subdirectory will</div>
<div class="diff add">+ also be created, if appropriate, under <varname>libdir</varname></div>
<div class="diff add">+ for dynamically loadable modules.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </note></div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ <variablelist></div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-includes=<replaceable>DIRECTORIES</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ <replaceable>DIRECTORIES</> is a colon-separated list of</div>
<div class="diff add">+ directories that will be added to the list the compiler</div>
<div class="diff add">+ searches for header files. If you have optional packages</div>
<div class="diff add">+ (such as GNU <application>Readline</>) installed in a non-standard</div>
<div class="diff add">+ location,</div>
<div class="diff add">+ you have to use this option and probably also the corresponding</div>
<div class="diff add">+ <option>--with-libraries</> option.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Example: <literal>--with-includes=/opt/gnu/include:/usr/sup/include</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-libraries=<replaceable>DIRECTORIES</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ <replaceable>DIRECTORIES</> is a colon-separated list of</div>
<div class="diff add">+ directories to search for libraries. You will probably have</div>
<div class="diff add">+ to use this option (and the corresponding</div>
<div class="diff add">+ <option>--with-includes</> option) if you have packages</div>
<div class="diff add">+ installed in non-standard locations.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Example: <literal>--with-libraries=/opt/gnu/lib:/usr/sup/lib</>.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Enables Native Language Support (<acronym>NLS</acronym>),</div>
<div class="diff add">+ that is, the ability to display a program's messages in a</div>
<div class="diff add">+ language other than English.</div>
<div class="diff add">+ <replaceable>LANGUAGES</replaceable> is a space separated</div>
<div class="diff add">+ list of codes of the languages that you want supported, for</div>
<div class="diff add">+ example <literal>--enable-nls='de fr'</>. (The intersection</div>
<div class="diff add">+ between your list and the set of actually provided</div>
<div class="diff add">+ translations will be computed automatically.) If you do not</div>
<div class="diff add">+ specify a list, then all available translations are</div>
<div class="diff add">+ installed.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ To use this option, you will need an implementation of the</div>
<div class="diff add">+ <application>Gettext</> API; see above.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-pgport=<replaceable>NUMBER</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Set <replaceable>NUMBER</> as the default port number for</div>
<div class="diff add">+ server and clients. The default is 5432. The port can always</div>
<div class="diff add">+ be changed later on, but if you specify it here then both</div>
<div class="diff add">+ server and clients will have the same default compiled in,</div>
<div class="diff add">+ which can be very convenient. Usually the only good reason</div>
<div class="diff add">+ to select a non-default value is if you intend to run multiple</div>
<div class="diff add">+ <productname>PostgreSQL</> servers on the same machine.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-perl</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build the <application>PL/Perl</> server-side language.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-python</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build the <application>PL/Python</> server-side language.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-tcl</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build the <application>PL/Tcl</> server-side language.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-tclconfig=<replaceable>DIRECTORY</replaceable></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Tcl installs the file <filename>tclConfig.sh</filename>, which</div>
<div class="diff add">+ contains configuration information needed to build modules</div>
<div class="diff add">+ interfacing to Tcl. This file is normally found automatically</div>
<div class="diff add">+ at a well-known location, but if you want to use a different</div>
<div class="diff add">+ version of Tcl you can specify the directory in which to look</div>
<div class="diff add">+ for it.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-krb4</option></term></div>
<div class="diff add">+ <term><option>--with-krb5</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build with support for Kerberos authentication. You can use</div>
<div class="diff add">+ either Kerberos version 4 or 5, but not both. On many</div>
<div class="diff add">+ systems, the Kerberos system is not installed in a location</div>
<div class="diff add">+ that is searched by default (e.g., <filename>/usr/include</>,</div>
<div class="diff add">+ <filename>/usr/lib</>), so you must use the options</div>
<div class="diff add">+ <option>--with-includes</> and <option>--with-libraries</> in</div>
<div class="diff add">+ addition to this option. <filename>configure</> will check</div>
<div class="diff add">+ for the required header files and libraries to make sure that</div>
<div class="diff add">+ your Kerberos installation is sufficient before proceeding.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-krb-srvnam=<replaceable>NAME</></option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ The name of the Kerberos service principal.</div>
<div class="diff add">+ <literal>postgres</literal> is the default. There's probably no</div>
<div class="diff add">+ reason to change this.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <indexterm></div>
<div class="diff add">+ <primary>OpenSSL</primary></div>
<div class="diff add">+ <seealso>SSL</seealso></div>
<div class="diff add">+ </indexterm></div>
<div class="diff add">+</div>
<div class="diff add">+ <term><option>--with-openssl</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build with support for <acronym>SSL</> (encrypted)</div>
<div class="diff add">+ connections. This requires the <productname>OpenSSL</></div>
<div class="diff add">+ package to be installed. <filename>configure</> will check</div>
<div class="diff add">+ for the required header files and libraries to make sure that</div>
<div class="diff add">+ your <productname>OpenSSL</> installation is sufficient</div>
<div class="diff add">+ before proceeding.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-pam</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build with <acronym>PAM</><indexterm><primary>PAM</></></div>
<div class="diff add">+ (Pluggable Authentication Modules) support.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--without-readline</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Prevents the use of the <application>Readline</> library. This disables</div>
<div class="diff add">+ command-line editing and history in</div>
<div class="diff add">+ <application>psql</application>, so it is not recommended.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--with-rendezvous</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Build with Rendezvous support.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--disable-spinlocks</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Allow the build to succeed even if <productname>PostgreSQL</></div>
<div class="diff add">+ has no CPU spinlock support for the platform. The lack of</div>
<div class="diff add">+ spinlock support will result in poor performance; therefore,</div>
<div class="diff add">+ this option should only be used if the build aborts and</div>
<div class="diff add">+ informs you that the platform lacks spinlock support. If this</div>
<div class="diff add">+ option is required to build <productname>PostgreSQL</> on</div>
<div class="diff add">+ your platform, please report the problem to the</div>
<div class="diff add">+ <productname>PostgreSQL</> developers.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--enable-thread-safety</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Make the client libraries thread-safe. This allows</div>
<div class="diff add">+ concurrent threads in <application>libpq</application> and</div>
<div class="diff add">+ <application>ECPG</application> programs to safely control</div>
<div class="diff add">+ their private connection handles.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--without-zlib</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Prevents the use of the <application>Zlib</> library. This disables</div>
<div class="diff add">+ compression support in <application>pg_dump</application>.</div>
<div class="diff add">+ This option is only intended for those rare systems where this</div>
<div class="diff add">+ library is not available.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--enable-debug</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Compiles all programs and libraries with debugging symbols.</div>
<div class="diff add">+ This means that you can run the programs through a debugger</div>
<div class="diff add">+ to analyze problems. This enlarges the size of the installed</div>
<div class="diff add">+ executables considerably, and on non-GCC compilers it usually</div>
<div class="diff add">+ also disables compiler optimization, causing slowdowns. However,</div>
<div class="diff add">+ having the symbols available is extremely helpful for dealing</div>
<div class="diff add">+ with any problems that may arise. Currently, this option is</div>
<div class="diff add">+ recommended for production installations only if you use GCC.</div>
<div class="diff add">+ But you should always have it on if you are doing development work</div>
<div class="diff add">+ or running a beta version.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--enable-cassert</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Enables <firstterm>assertion</> checks in the server, which test for</div>
<div class="diff add">+ many <quote>can't happen</> conditions. This is invaluable for</div>
<div class="diff add">+ code development purposes, but the tests slow things down a little.</div>
<div class="diff add">+ Also, having the tests turned on won't necessarily enhance the</div>
<div class="diff add">+ stability of your server! The assertion checks are not categorized</div>
<div class="diff add">+ for severity, and so what might be a relatively harmless bug will</div>
<div class="diff add">+ still lead to server restarts if it triggers an assertion</div>
<div class="diff add">+ failure. Currently, this option is not recommended for</div>
<div class="diff add">+ production use, but you should have it on for development work</div>
<div class="diff add">+ or when running a beta version.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ <varlistentry></div>
<div class="diff add">+ <term><option>--enable-depend</option></term></div>
<div class="diff add">+ <listitem></div>
<div class="diff add">+ <para></div>
<div class="diff add">+ Enables automatic dependency tracking. With this option, the</div>
<div class="diff add">+ makefiles are set up so that all affected object files will</div>
<div class="diff add">+ be rebuilt when any header file is changed. This is useful</div>
<div class="diff add">+ if you are doing development work, but is just wasted overhead</div>
<div class="diff add">+ if you intend only to compile once and install. At present,</div>
<div class="diff add">+ this option will work only if you use GCC.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </listitem></div>
<div class="diff add">+ </varlistentry></div>
<div class="diff add">+</div>
<div class="diff add">+ </variablelist></div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ If you prefer a C compiler different from the one</div>
<div class="diff add">+ <filename>configure</filename> picks then you can set the</div>
<div class="diff add">+ environment variable <envar>CC</> to the program of your choice.</div>
<div class="diff add">+ By default, <filename>configure</filename> will pick</div>
<div class="diff add">+ <filename>gcc</filename> unless this is inappropriate for the</div>
<div class="diff add">+ platform. Similarly, you can override the default compiler flags</div>
<div class="diff add">+ with the <envar>CFLAGS</envar> variable.</div>
<div class="diff add">+ </para></div>
<div class="diff add">+</div>
<div class="diff add">+ <para></div>
<div class="diff add">+ You can specify environment variables on the</div>
<div class="diff add">+ <filename>configure</filename> command line, for example:</div>
<div class="diff add">+<screen></div>
<div class="diff add">+<userinput>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'</></div>
<div class="diff add">+</screen></div>
<div class="diff add">+ </para></div>
<div class="diff add">+ </step></div>
<div class="diff add">+</div>
<div class="diff add">+ <step></div>
<div class="diff add">+ <title>Build
+
+
+ To start the build, type
+
+gmake
+
+ (Remember to use GNU make.) The build
+ may take anywhere from 5 minutes to half an hour depending on your
+ hardware. The last line displayed should be
+
+All of PostgreSQL is successfully made. Ready to install.
+
+
+
+
+
+ Regression Tests
+
+
+ regression test
+
+
+
+ If you want to test the newly built server before you install it,
+ you can run the regression tests at this point. The regression
+ tests are a test suite to verify that PostgreSQL
+ runs on your machine in the way the developers expected it
+ to. Type
+
+gmake check
+
+ (This won't work as root; do it as an unprivileged user.)
+
+ src/test/regress/README and the
+ documentation contain]]>
+ contains]]>
+ detailed information about interpreting the test results. You can
+ repeat this test at any later time by issuing the same command.
+
+
+
+
+ Installing The Files
+
+
+
+ If you are upgrading an existing system and are going to install
+ the new files over the old ones, then you should have backed up
+ your data and shut down the old server by now, as explained in
+ above.
+
+
+
+
+ To install PostgreSQL enter
+
+gmake install
+
+ This will install files into the directories that were specified
+ in . 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.
+
+
+
+ You can use gmake install-strip instead of
+ gmake install 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. install-strip
+ 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.
+
+
+
+ The standard installation provides all the header files needed for client
+ application development as well as for any server-side program
+ development (such as custom functions or data types written in C).
+
+
+
+ Client-only installation:
+
+ If you want to install only the client applications and
+ interface libraries, then you can use these commands:
+
+gmake -C src/bin install
+gmake -C src/include install
+gmake -C src/interfaces install
+gmake -C doc install
+
+
+
+
+
+
+
+ Registering <application>eventlog</> on <systemitem </div>
<div class="diff add">+ class="osname">Windows</>:
+
+ To register a Windows eventlog
+ library with the operating system, issue this command after installation:
+
+regsvr32 pgsql_library_directory/pgevent.dll
+
+ This creates registry entries used by the event viewer.
+
+
+
+
+ Uninstallation:
+
+ To undo the installation use the command gmake
+ uninstall. However, this will not remove any created directories.
+
+
+
+
+ Cleaning:
+
+
+ After the installation you can make room by removing the built
+ files from the source tree with the command gmake
+ clean. This will preserve the files made by the configure
+ program, so that you can rebuild everything with gmake
+ later on. To reset the source tree to the state in which it was
+ distributed, use 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.
+
+
+
+
+ If you perform a build and then discover that your configure
+ options were wrong, or if you change anything that configure
+ investigates (for example, software upgrades), then it's a good
+ idea to do gmake distclean before reconfiguring and
+ rebuilding. Without this, your changes in configuration choices
+ may not propagate everywhere they need to.
+
+
+
+
+ Post-Installation Setup
+
+
+ Shared Libraries
+
+
+ shared library
+
+
+
+ On some systems that have shared libraries (which most systems do)
+ you need to tell your system how to find the newly installed
+ shared libraries. The systems on which this is
+ not necessary include
+ class="osname">BSD/OS, FreeBSD,
+ HP-UX,
+ class="osname">IRIX, Linux,
+ NetBSD,
+ class="osname">OpenBSD, Tru64
+ UNIX (formerly Digital UNIX), and
+ Solaris.
+
+
+
+ The method to set the shared library search path varies between
+ platforms, but the most widely usable method is to set the
+ environment variable LD_LIBRARY_PATH like so: In Bourne
+ shells (sh, ksh, bash, zsh)
+
+LD_LIBRARY_PATH=/usr/local/pgsql/lib
+export LD_LIBRARY_PATH
+
+ or in csh or tcsh
+
+setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
+
+ Replace /usr/local/pgsql/lib with whatever you set
+
+ You should put these commands into a shell start-up file such as
+ /etc/profile or ~/.bash_profile. Some
+ good information about the caveats associated with this method can
+ be found at
+ url="http://www.visi.com/~barr/ldpath.html">.
+
+
+
+ On some systems it might be preferable to set the environment
+ variable LD_RUN_PATHbefore
+ building.
+
+
+
+ On Cygwin, put the library
+ directory in the PATH or move the
+ .dll files into the bin
+ directory.
+
+
+
+ If in doubt, refer to the manual pages of your system (perhaps
+ ld.so or rld). If you later
+ on get a message like
+
+psql: error in loading shared libraries
+libpq.so.2.1: cannot open shared object file: No such file or directory
+
+ then this step was necessary. Simply take care of it then.
+
+
+
+
+ ldconfig
+
+ If you are on BSD/OS,
+ class="osname">Linux, or SunOS 4
+ and you have root access you can run
+
+/sbin/ldconfig /usr/local/pgsql/lib
+
+ (or equivalent directory) after installation to enable the
+ run-time linker to find the shared libraries faster. Refer to the
+ manual page of ldconfig for more information. On
+ FreeBSD,
+ class="osname">NetBSD, and
+ class="osname">OpenBSD the command is
+
+/sbin/ldconfig -m /usr/local/pgsql/lib
+
+ instead. Other systems are not known to have an equivalent
+ command.
+
+
+
+
+ Environment Variables
+
+
+ PATH
+
+
+
+ If you installed into /usr/local/pgsql or some other
+ location that is not searched for programs by default, you should
+ add /usr/local/pgsql/bin (or whatever you set
+
+ into your PATH. Strictly speaking, this is not
+ necessary, but it will make the use of PostgreSQL
+ much more convenient.
+
+
+
+ To do this, add the following to your shell start-up file, such as
+ ~/.bash_profile (or /etc/profile, if you
+ want it to affect every user):
+
+PATH=/usr/local/pgsql/bin:$PATH
+export PATH
+
+ If you are using csh or tcsh, then use this command:
+
+set path = ( /usr/local/pgsql/bin $path )
+
+
+
+
+
+ MANPATH
+
+ To enable your system to find the man
+ documentation, you need to add lines like the following to a
+ shell start-up file unless you installed into a location that is
+ searched by default.
+
+MANPATH=/usr/local/pgsql/man:$MANPATH
+export MANPATH
+
+
+
+
+ The environment variables PGHOST and 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
+ user that plans to use the database sets PGHOST. This
+ is not required, however: the settings can be communicated via command
+ line options to most client programs.
+
+
+
+
+
+
+
+ Getting Started
+
+
+ The following is a quick summary of how to get PostgreSQL up and
+ running once installed. The main documentation contains more information.
+
+
+
+
+
+ Create a user account for the PostgreSQL
+ server. This is the user the server will run as. For production
+ use you should create a separate, unprivileged account
+ (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.
+
+adduser postgres
+
+
+
+
+
+
+ Create a database installation with the initdb
+ command. To run initdb you must be logged in to your
projects / postgresql.git / commitdiff