Baoding-FenShuaJiang
/
Green_GoodERP18_FSJ_Standard
Прати 1
Волим 0
Вики 捐赠
gooderp18绿色标准版
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Грана: master
Гране Ознаке
${ item.name }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Green_GoodERP18_FSJ_Standard/PostgreSQL/doc/postgresql/html/install-procedure.html

754 lines
54KB
Датотека Пермалинк Blame Историја 

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.4. Installation Procedure</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="install-getsource.html" title="16.3. Getting the Source" /><link rel="next" href="install-post.html" title="16.5. Post-Installation Setup" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">16.4. Installation Procedure</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="install-getsource.html" title="16.3. Getting the Source">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="installation.html" title="Chapter 16. Installation from Source Code">Up</a></td><th width="60%" align="center">Chapter 16. Installation from Source Code</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="install-post.html" title="16.5. Post-Installation Setup">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="INSTALL-PROCEDURE"><div class="titlepage"><div><div><h2 class="title" style="clear: both">16.4. Installation Procedure</h2></div></div></div><div class="procedure"><ol class="procedure" type="1"><li class="step" id="CONFIGURE"><p class="title"><strong>Configuration</strong></p><a id="id-1.6.3.8.2.1.2" class="indexterm"></a><p>

  3.     The first step of the installation procedure is to configure the

  4.     source tree for your system and choose the options you would like.

  5.     This is done by running the <code class="filename">configure</code> script. For a

  6.     default installation simply enter:

  7. </p><pre class="screen">

  8. <strong class="userinput"><code>./configure</code></strong>

  9. </pre><p>

  10.     This script will run a number of tests to determine values for various

  11.     system dependent variables and detect any quirks of your

  12.     operating system, and finally will create several files in the

  13.     build tree to record what it found.  You can also run

  14.     <code class="filename">configure</code> in a directory outside the source

  15.     tree, if you want to keep the build directory separate.  This

  16.     procedure is also called a

  17.     <a id="id-1.6.3.8.2.1.3.4" class="indexterm"></a><em class="firstterm">VPATH</em>

  18.     build.  Here's how:

  19. </p><pre class="screen">

  20. <strong class="userinput"><code>mkdir build_dir</code></strong>

  21. <strong class="userinput"><code>cd build_dir</code></strong>

  22. <strong class="userinput"><code>/path/to/source/tree/configure [options go here]</code></strong>

  23. <strong class="userinput"><code>make</code></strong>

  24. </pre><p>

  25.    </p><p>

  26.     The default configuration will build the server and utilities, as

  27.     well as all client applications and interfaces that require only a

  28.     C compiler. All files will be installed under

  29.     <code class="filename">/usr/local/pgsql</code> by default.

  30.    </p><p>

  31.     You can customize the build and installation process by supplying one

  32.     or more of the following command line options to

  33.     <code class="filename">configure</code>:

  34. 

  35.      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="option">--prefix=<em class="replaceable"><code>PREFIX</code></em></code></span></dt><dd><p>

  36.          Install all files under the directory <em class="replaceable"><code>PREFIX</code></em>

  37.          instead of <code class="filename">/usr/local/pgsql</code>. The actual

  38.          files will be installed into various subdirectories; no files

  39.          will ever be installed directly into the

  40.          <em class="replaceable"><code>PREFIX</code></em> directory.

  41.         </p><p>

  42.          If you have special needs, you can also customize the

  43.          individual subdirectories with the following options. However,

  44.          if you leave these with their defaults, the installation will be

  45.          relocatable, meaning you can move the directory after

  46.          installation. (The <code class="literal">man</code> and <code class="literal">doc</code>

  47.          locations are not affected by this.)

  48.         </p><p>

  49.          For relocatable installs, you might want to use

  50.          <code class="filename">configure</code>'s <code class="literal">--disable-rpath</code>

  51.          option.  Also, you will need to tell the operating system how

  52.          to find the shared libraries.

  53.         </p></dd><dt><span class="term"><code class="option">--exec-prefix=<em class="replaceable"><code>EXEC-PREFIX</code></em></code></span></dt><dd><p>

  54.          You can install architecture-dependent files under a

  55.          different prefix, <em class="replaceable"><code>EXEC-PREFIX</code></em>, than what

  56.          <em class="replaceable"><code>PREFIX</code></em> was set to. This can be useful to

  57.          share architecture-independent files between hosts. If you

  58.          omit this, then <em class="replaceable"><code>EXEC-PREFIX</code></em> is set equal to

  59.          <em class="replaceable"><code>PREFIX</code></em> and both architecture-dependent and

  60.          independent files will be installed under the same tree,

  61.          which is probably what you want.

  62.         </p></dd><dt><span class="term"><code class="option">--bindir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  63.          Specifies the directory for executable programs. The default

  64.          is <code class="filename"><em class="replaceable"><code>EXEC-PREFIX</code></em>/bin</code>, which

  65.          normally means <code class="filename">/usr/local/pgsql/bin</code>.

  66.         </p></dd><dt><span class="term"><code class="option">--sysconfdir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  67.          Sets the directory for various configuration files,

  68.          <code class="filename"><em class="replaceable"><code>PREFIX</code></em>/etc</code> by default.

  69.         </p></dd><dt><span class="term"><code class="option">--libdir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  70.          Sets the location to install libraries and dynamically loadable

  71.          modules. The default is

  72.          <code class="filename"><em class="replaceable"><code>EXEC-PREFIX</code></em>/lib</code>.

  73.         </p></dd><dt><span class="term"><code class="option">--includedir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  74.          Sets the directory for installing C and C++ header files. The

  75.          default is <code class="filename"><em class="replaceable"><code>PREFIX</code></em>/include</code>.

  76.         </p></dd><dt><span class="term"><code class="option">--datarootdir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  77.          Sets the root directory for various types of read-only data

  78.          files.  This only sets the default for some of the following

  79.          options.  The default is

  80.          <code class="filename"><em class="replaceable"><code>PREFIX</code></em>/share</code>.

  81.         </p></dd><dt><span class="term"><code class="option">--datadir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  82.          Sets the directory for read-only data files used by the

  83.          installed programs. The default is

  84.          <code class="filename"><em class="replaceable"><code>DATAROOTDIR</code></em></code>. Note that this has

  85.          nothing to do with where your database files will be placed.

  86.         </p></dd><dt><span class="term"><code class="option">--localedir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  87.          Sets the directory for installing locale data, in particular

  88.          message translation catalog files.  The default is

  89.          <code class="filename"><em class="replaceable"><code>DATAROOTDIR</code></em>/locale</code>.

  90.         </p></dd><dt><span class="term"><code class="option">--mandir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  91.          The man pages that come with <span class="productname">PostgreSQL</span> will be installed under

  92.          this directory, in their respective

  93.          <code class="filename">man<em class="replaceable"><code>x</code></em></code> subdirectories.

  94.          The default is <code class="filename"><em class="replaceable"><code>DATAROOTDIR</code></em>/man</code>.

  95.         </p></dd><dt><span class="term"><code class="option">--docdir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  96.          Sets the root directory for installing documentation files,

  97.          except <span class="quote">“<span class="quote">man</span>”</span> pages.  This only sets the default for

  98.          the following options.  The default value for this option is

  99.          <code class="filename"><em class="replaceable"><code>DATAROOTDIR</code></em>/doc/postgresql</code>.

  100.         </p></dd><dt><span class="term"><code class="option">--htmldir=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  101.          The HTML-formatted documentation for

  102.          <span class="productname">PostgreSQL</span> will be installed under

  103.          this directory.  The default is

  104.          <code class="filename"><em class="replaceable"><code>DATAROOTDIR</code></em></code>.

  105.         </p></dd></dl></div><p>

  106. 

  107.      </p><div class="note"><h3 class="title">Note</h3><p>

  108.        Care has been taken to make it possible to install

  109.        <span class="productname">PostgreSQL</span> into shared installation locations

  110.        (such as <code class="filename">/usr/local/include</code>) without

  111.        interfering with the namespace of the rest of the system. First,

  112.        the string <span class="quote">“<span class="quote"><code class="literal">/postgresql</code></span>”</span> is

  113.        automatically appended to <code class="varname">datadir</code>,

  114.        <code class="varname">sysconfdir</code>, and <code class="varname">docdir</code>,

  115.        unless the fully expanded directory name already contains the

  116.        string <span class="quote">“<span class="quote"><code class="literal">postgres</code></span>”</span> or

  117.        <span class="quote">“<span class="quote"><code class="literal">pgsql</code></span>”</span>. For example, if you choose

  118.        <code class="filename">/usr/local</code> as prefix, the documentation will

  119.        be installed in <code class="filename">/usr/local/doc/postgresql</code>,

  120.        but if the prefix is <code class="filename">/opt/postgres</code>, then it

  121.        will be in <code class="filename">/opt/postgres/doc</code>. The public C

  122.        header files of the client interfaces are installed into

  123.        <code class="varname">includedir</code> and are namespace-clean. The

  124.        internal header files and the server header files are installed

  125.        into private directories under <code class="varname">includedir</code>. See

  126.        the documentation of each interface for information about how to

  127.        access its header files. Finally, a private subdirectory will

  128.        also be created, if appropriate, under <code class="varname">libdir</code>

  129.        for dynamically loadable modules.

  130.       </p></div><p>

  131.     </p><p>

  132.      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="option">--with-extra-version=<em class="replaceable"><code>STRING</code></em></code></span></dt><dd><p>

  133.          Append <em class="replaceable"><code>STRING</code></em> to the PostgreSQL version number.  You

  134.          can use this, for example, to mark binaries built from unreleased Git

  135.          snapshots or containing custom patches with an extra version string

  136.          such as a <code class="command">git describe</code> identifier or a

  137.          distribution package release number.

  138.         </p></dd><dt><span class="term"><code class="option">--with-includes=<em class="replaceable"><code>DIRECTORIES</code></em></code></span></dt><dd><p>

  139.          <em class="replaceable"><code>DIRECTORIES</code></em> is a colon-separated list of

  140.          directories that will be added to the list the compiler

  141.          searches for header files. If you have optional packages

  142.          (such as GNU <span class="application">Readline</span>) installed in a non-standard

  143.          location,

  144.          you have to use this option and probably also the corresponding

  145.          <code class="option">--with-libraries</code> option.

  146.         </p><p>

  147.          Example: <code class="literal">--with-includes=/opt/gnu/include:/usr/sup/include</code>.

  148.         </p></dd><dt><span class="term"><code class="option">--with-libraries=<em class="replaceable"><code>DIRECTORIES</code></em></code></span></dt><dd><p>

  149.          <em class="replaceable"><code>DIRECTORIES</code></em> is a colon-separated list of

  150.          directories to search for libraries. You will probably have

  151.          to use this option (and the corresponding

  152.          <code class="option">--with-includes</code> option) if you have packages

  153.          installed in non-standard locations.

  154.         </p><p>

  155.          Example: <code class="literal">--with-libraries=/opt/gnu/lib:/usr/sup/lib</code>.

  156.         </p></dd><dt><span class="term"><code class="option">--enable-nls[<span class="optional">=<em class="replaceable"><code>LANGUAGES</code></em></span>]</code></span></dt><dd><p>

  157.          Enables Native Language Support (<acronym class="acronym">NLS</acronym>),

  158.          that is, the ability to display a program's messages in a

  159.          language other than English.

  160.          <em class="replaceable"><code>LANGUAGES</code></em> is an optional space-separated

  161.          list of codes of the languages that you want supported, for

  162.          example <code class="literal">--enable-nls='de fr'</code>.  (The intersection

  163.          between your list and the set of actually provided

  164.          translations will be computed automatically.)  If you do not

  165.          specify a list, then all available translations are

  166.          installed.

  167.         </p><p>

  168.          To use this option, you will need an implementation of the

  169.          <span class="application">Gettext</span> API; see above.

  170.         </p></dd><dt><span class="term"><code class="option">--with-pgport=<em class="replaceable"><code>NUMBER</code></em></code></span></dt><dd><p>

  171.          Set <em class="replaceable"><code>NUMBER</code></em> as the default port number for

  172.          server and clients. The default is 5432. The port can always

  173.          be changed later on, but if you specify it here then both

  174.          server and clients will have the same default compiled in,

  175.          which can be very convenient.  Usually the only good reason

  176.          to select a non-default value is if you intend to run multiple

  177.          <span class="productname">PostgreSQL</span> servers on the same machine.

  178.         </p></dd><dt><span class="term"><code class="option">--with-perl</code></span></dt><dd><p>

  179.          Build the <span class="application">PL/Perl</span> server-side language.

  180.         </p></dd><dt><span class="term"><code class="option">--with-python</code></span></dt><dd><p>

  181.          Build the <span class="application">PL/Python</span> server-side language.

  182.         </p></dd><dt><span class="term"><code class="option">--with-tcl</code></span></dt><dd><p>

  183.          Build the <span class="application">PL/Tcl</span> server-side language.

  184.         </p></dd><dt><span class="term"><code class="option">--with-tclconfig=<em class="replaceable"><code>DIRECTORY</code></em></code></span></dt><dd><p>

  185.          Tcl installs the file <code class="filename">tclConfig.sh</code>, which

  186.          contains configuration information needed to build modules

  187.          interfacing to Tcl. This file is normally found automatically

  188.          at a well-known location, but if you want to use a different

  189.          version of Tcl you can specify the directory in which to look

  190.          for it.

  191.         </p></dd><dt><span class="term"><code class="option">--with-gssapi</code></span></dt><dd><p>

  192.          Build with support for GSSAPI authentication. On many

  193.          systems, the GSSAPI (usually a part of the Kerberos installation)

  194.          system is not installed in a location

  195.          that is searched by default (e.g., <code class="filename">/usr/include</code>,

  196.          <code class="filename">/usr/lib</code>), so you must use the options

  197.          <code class="option">--with-includes</code> and <code class="option">--with-libraries</code> in

  198.          addition to this option.  <code class="filename">configure</code> will check

  199.          for the required header files and libraries to make sure that

  200.          your GSSAPI installation is sufficient before proceeding.

  201.         </p></dd><dt><span class="term"><code class="option">--with-krb-srvnam=<em class="replaceable"><code>NAME</code></em></code></span></dt><dd><p>

  202.          The default name of the Kerberos service principal used

  203.          by GSSAPI.

  204.          <code class="literal">postgres</code> is the default. There's usually no

  205.          reason to change this unless you have a Windows environment,

  206.          in which case it must be set to upper case

  207.          <code class="literal">POSTGRES</code>.

  208.         </p></dd><dt id="CONFIGURE-WITH-LLVM"><span class="term"><code class="option">--with-llvm</code></span></dt><dd><p>

  209.          Build with support for <span class="productname">LLVM</span> based

  210.          <acronym class="acronym">JIT</acronym> compilation<span class="phrase"> (see <a class="xref" href="jit.html" title="Chapter 31. Just-in-Time Compilation (JIT)">Chapter 31</a>)</span>.  This

  211.          requires the <span class="productname">LLVM</span> library to be installed.

  212.          The minimum required version of <span class="productname">LLVM</span> is

  213.          currently 3.9.

  214.         </p><p>

  215.          <code class="command">llvm-config</code><a id="id-1.6.3.8.2.1.6.1.12.2.2.2" class="indexterm"></a>

  216.          will be used to find the required compilation options.

  217.          <code class="command">llvm-config</code>, and then

  218.          <code class="command">llvm-config-$major-$minor</code> for all supported

  219.          versions, will be searched on <code class="envar">PATH</code>. If that would not

  220.          yield the correct binary, use <code class="envar">LLVM_CONFIG</code> to specify a

  221.          path to the correct <code class="command">llvm-config</code>. For example

  222. </p><pre class="programlisting">

  223. ./configure ... --with-llvm LLVM_CONFIG='/path/to/llvm/bin/llvm-config'

  224. </pre><p>

  225.         </p><p>

  226.          <span class="productname">LLVM</span> support requires a compatible

  227.          <code class="command">clang</code> compiler (specified, if necessary, using the

  228.          <code class="envar">CLANG</code> environment variable), and a working C++

  229.          compiler (specified, if necessary, using the <code class="envar">CXX</code>

  230.          environment variable).

  231.         </p></dd><dt><span class="term"><code class="option">--with-icu</code></span></dt><dd><p>

  232.          Build with support for

  233.          the <span class="productname">ICU</span><a id="id-1.6.3.8.2.1.6.1.13.2.1.2" class="indexterm"></a>

  234.          library.  This requires the <span class="productname">ICU4C</span> package

  235.          to be installed.  The minimum required version

  236.          of <span class="productname">ICU4C</span> is currently 4.2.

  237.         </p><p>

  238.          By default,

  239.          <span class="productname">pkg-config</span><a id="id-1.6.3.8.2.1.6.1.13.2.2.2" class="indexterm"></a>

  240.          will be used to find the required compilation options.  This is

  241.          supported for <span class="productname">ICU4C</span> version 4.6 and later.

  242.          For older versions, or if <span class="productname">pkg-config</span> is

  243.          not available, the variables <code class="envar">ICU_CFLAGS</code>

  244.          and <code class="envar">ICU_LIBS</code> can be specified

  245.          to <code class="filename">configure</code>, like in this example:

  246. </p><pre class="programlisting">

  247. ./configure ... --with-icu ICU_CFLAGS='-I/some/where/include' ICU_LIBS='-L/some/where/lib -licui18n -licuuc -licudata'

  248. </pre><p>

  249.          (If <span class="productname">ICU4C</span> is in the default search path

  250.          for the compiler, then you still need to specify a nonempty string in

  251.          order to avoid use of <span class="productname">pkg-config</span>, for

  252.          example, <code class="literal">ICU_CFLAGS=' '</code>.)

  253.         </p></dd><dt><span class="term"><code class="option">--with-openssl</code>

  254.        <a id="id-1.6.3.8.2.1.6.1.14.1.2" class="indexterm"></a>

  255.        </span></dt><dd><p>

  256.          Build with support for <acronym class="acronym">SSL</acronym> (encrypted)

  257.          connections. This requires the <span class="productname">OpenSSL</span>

  258.          package to be installed.  <code class="filename">configure</code> will check

  259.          for the required header files and libraries to make sure that

  260.          your <span class="productname">OpenSSL</span> installation is sufficient

  261.          before proceeding.

  262.         </p></dd><dt><span class="term"><code class="option">--with-pam</code></span></dt><dd><p>

  263.          Build with <acronym class="acronym">PAM</acronym><a id="id-1.6.3.8.2.1.6.1.15.2.1.2" class="indexterm"></a>

  264.          (Pluggable Authentication Modules) support.

  265.         </p></dd><dt><span class="term"><code class="option">--with-bsd-auth</code></span></dt><dd><p>

  266.          Build with BSD Authentication support.

  267.          (The BSD Authentication framework is

  268.          currently only available on OpenBSD.)

  269.         </p></dd><dt><span class="term"><code class="option">--with-ldap</code></span></dt><dd><p>

  270.          Build with <acronym class="acronym">LDAP</acronym><a id="id-1.6.3.8.2.1.6.1.17.2.1.2" class="indexterm"></a>

  271.          support for authentication and connection parameter lookup (see

  272.          <span id="INSTALL-LDAP-LINKS" class="phrase"><a class="xref" href="libpq-ldap.html" title="33.17. LDAP Lookup of Connection Parameters">Section 33.17</a> and

  273.          <a class="xref" href="auth-ldap.html" title="20.10. LDAP Authentication">Section 20.10</a></span> for more information). On Unix,

  274.          this requires the <span class="productname">OpenLDAP</span> package to be

  275.          installed. On Windows, the default <span class="productname">WinLDAP</span>

  276.          library is used.  <code class="filename">configure</code> will check for the required

  277.          header files and libraries to make sure that your

  278.          <span class="productname">OpenLDAP</span> installation is sufficient before

  279.          proceeding.

  280.         </p></dd><dt><span class="term"><code class="option">--with-systemd</code></span></dt><dd><p>

  281.          Build with support

  282.          for <span class="application">systemd</span><a id="id-1.6.3.8.2.1.6.1.18.2.1.2" class="indexterm"></a>

  283.          service notifications.  This improves integration if the server binary

  284.          is started under <span class="application">systemd</span> but has no impact

  285.          otherwise<span class="phrase">; see <a class="xref" href="server-start.html" title="18.3. Starting the Database Server">Section 18.3</a> for more

  286.          information</span>.  <span class="application">libsystemd</span> and the

  287.          associated header files need to be installed to be able to use this

  288.          option.

  289.         </p></dd><dt><span class="term"><code class="option">--without-readline</code></span></dt><dd><p>

  290.          Prevents use of the <span class="application">Readline</span> library

  291.          (and <span class="application">libedit</span> as well).  This option disables

  292.          command-line editing and history in

  293.          <span class="application">psql</span>, so it is not recommended.

  294.         </p></dd><dt><span class="term"><code class="option">--with-libedit-preferred</code></span></dt><dd><p>

  295.          Favors the use of the BSD-licensed <span class="application">libedit</span> library

  296.          rather than GPL-licensed <span class="application">Readline</span>.  This option

  297.          is significant only if you have both libraries installed; the

  298.          default in that case is to use <span class="application">Readline</span>.

  299.         </p></dd><dt><span class="term"><code class="option">--with-bonjour</code></span></dt><dd><p>

  300.          Build with Bonjour support.  This requires Bonjour support

  301.          in your operating system.  Recommended on macOS.

  302.         </p></dd><dt><span class="term"><code class="option">--with-uuid=<em class="replaceable"><code>LIBRARY</code></em></code></span></dt><dd><p>

  303.          Build the <a class="xref" href="uuid-ossp.html" title="F.44. uuid-ossp">uuid-ossp</a> module

  304.          (which provides functions to generate UUIDs), using the specified

  305.          UUID library.<a id="id-1.6.3.8.2.1.6.1.22.2.1.2" class="indexterm"></a>

  306.          <em class="replaceable"><code>LIBRARY</code></em> must be one of:

  307.         </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>

  308.            <code class="option">bsd</code> to use the UUID functions found in FreeBSD, NetBSD,

  309.            and some other BSD-derived systems

  310.           </p></li><li class="listitem"><p>

  311.            <code class="option">e2fs</code> to use the UUID library created by

  312.            the <code class="literal">e2fsprogs</code> project; this library is present in most

  313.            Linux systems and in macOS, and can be obtained for other

  314.            platforms as well

  315.           </p></li><li class="listitem"><p>

  316.            <code class="option">ossp</code> to use the <a class="ulink" href="http://www.ossp.org/pkg/lib/uuid/" target="_top">OSSP UUID library</a>

  317.           </p></li></ul></div></dd><dt><span class="term"><code class="option">--with-ossp-uuid</code></span></dt><dd><p>

  318.          Obsolete equivalent of <code class="literal">--with-uuid=ossp</code>.

  319.         </p></dd><dt><span class="term"><code class="option">--with-libxml</code></span></dt><dd><p>

  320.          Build with libxml2, enabling SQL/XML support.  Libxml2 version 2.6.23 or

  321.          later is required for this feature.

  322.         </p><p>

  323.          To detect the required compiler and linker options, PostgreSQL will

  324.          query <code class="command">pkg-config</code>, if that is installed and knows

  325.          about libxml2.  Otherwise the program <code class="command">xml2-config</code>,

  326.          which is installed by libxml2, will be used if it is found.  Use

  327.          of <code class="command">pkg-config</code> is preferred, because it can deal

  328.          with multi-architecture installations better.

  329.         </p><p>

  330.          To use a libxml2 installation that is in an unusual location, you

  331.          can set <code class="command">pkg-config</code>-related environment

  332.          variables (see its documentation), or set the environment variable

  333.          <code class="envar">XML2_CONFIG</code> to point to

  334.          the <code class="command">xml2-config</code> program belonging to the libxml2

  335.          installation, or set the variables <code class="envar">XML2_CFLAGS</code>

  336.          and <code class="envar">XML2_LIBS</code>.  (If <code class="command">pkg-config</code> is

  337.          installed, then to override its idea of where libxml2 is you must

  338.          either set <code class="envar">XML2_CONFIG</code> or set

  339.          both <code class="envar">XML2_CFLAGS</code> and <code class="envar">XML2_LIBS</code> to

  340.          nonempty strings.)

  341.         </p></dd><dt><span class="term"><code class="option">--with-libxslt</code></span></dt><dd><p>

  342.          Use libxslt when building the

  343.          <a class="xref" href="xml2.html" title="F.45. xml2">xml2</a>

  344.          module.  <span class="application">xml2</span> relies on this library

  345.          to perform XSL transformations of XML.

  346.         </p></dd><dt><span class="term"><code class="option">--disable-float4-byval</code></span></dt><dd><p>

  347.          Disable passing float4 values <span class="quote">“<span class="quote">by value</span>”</span>, causing them

  348.          to be passed <span class="quote">“<span class="quote">by reference</span>”</span> instead.  This option costs

  349.          performance, but may be needed for compatibility with old

  350.          user-defined functions that are written in C and use the

  351.          <span class="quote">“<span class="quote">version 0</span>”</span> calling convention.  A better long-term

  352.          solution is to update any such functions to use the

  353.          <span class="quote">“<span class="quote">version 1</span>”</span> calling convention.

  354.         </p></dd><dt><span class="term"><code class="option">--disable-float8-byval</code></span></dt><dd><p>

  355.          Disable passing float8 values <span class="quote">“<span class="quote">by value</span>”</span>, causing them

  356.          to be passed <span class="quote">“<span class="quote">by reference</span>”</span> instead.  This option costs

  357.          performance, but may be needed for compatibility with old

  358.          user-defined functions that are written in C and use the

  359.          <span class="quote">“<span class="quote">version 0</span>”</span> calling convention.  A better long-term

  360.          solution is to update any such functions to use the

  361.          <span class="quote">“<span class="quote">version 1</span>”</span> calling convention.

  362.          Note that this option affects not only float8, but also int8 and some

  363.          related types such as timestamp.

  364.          On 32-bit platforms, <code class="option">--disable-float8-byval</code> is the default

  365.          and it is not allowed to select <code class="option">--enable-float8-byval</code>.

  366.         </p></dd><dt><span class="term"><code class="option">--with-segsize=<em class="replaceable"><code>SEGSIZE</code></em></code></span></dt><dd><p>

  367.          Set the <em class="firstterm">segment size</em>, in gigabytes.  Large tables are

  368.          divided into multiple operating-system files, each of size equal

  369.          to the segment size.  This avoids problems with file size limits

  370.          that exist on many platforms.  The default segment size, 1 gigabyte,

  371.          is safe on all supported platforms.  If your operating system has

  372.          <span class="quote">“<span class="quote">largefile</span>”</span> support (which most do, nowadays), you can use

  373.          a larger segment size.  This can be helpful to reduce the number of

  374.          file descriptors consumed when working with very large tables.

  375.          But be careful not to select a value larger than is supported

  376.          by your platform and the file systems you intend to use.  Other

  377.          tools you might wish to use, such as <span class="application">tar</span>, could

  378.          also set limits on the usable file size.

  379.          It is recommended, though not absolutely required, that this value

  380.          be a power of 2.

  381.          Note that changing this value requires an initdb.

  382.         </p></dd><dt><span class="term"><code class="option">--with-blocksize=<em class="replaceable"><code>BLOCKSIZE</code></em></code></span></dt><dd><p>

  383.          Set the <em class="firstterm">block size</em>, in kilobytes.  This is the unit

  384.          of storage and I/O within tables.  The default, 8 kilobytes,

  385.          is suitable for most situations; but other values may be useful

  386.          in special cases.

  387.          The value must be a power of 2 between 1 and 32 (kilobytes).

  388.          Note that changing this value requires an initdb.

  389.         </p></dd><dt><span class="term"><code class="option">--with-wal-blocksize=<em class="replaceable"><code>BLOCKSIZE</code></em></code></span></dt><dd><p>

  390.          Set the <em class="firstterm">WAL block size</em>, in kilobytes.  This is the unit

  391.          of storage and I/O within the WAL log.  The default, 8 kilobytes,

  392.          is suitable for most situations; but other values may be useful

  393.          in special cases.

  394.          The value must be a power of 2 between 1 and 64 (kilobytes).

  395.          Note that changing this value requires an initdb.

  396.         </p></dd><dt><span class="term"><code class="option">--disable-spinlocks</code></span></dt><dd><p>

  397.          Allow the build to succeed even if <span class="productname">PostgreSQL</span>

  398.          has no CPU spinlock support for the platform.  The lack of

  399.          spinlock support will result in poor performance; therefore,

  400.          this option should only be used if the build aborts and

  401.          informs you that the platform lacks spinlock support. If this

  402.          option is required to build <span class="productname">PostgreSQL</span> on

  403.          your platform, please report the problem to the

  404.          <span class="productname">PostgreSQL</span> developers.

  405.         </p></dd><dt><span class="term"><code class="option">--disable-thread-safety</code></span></dt><dd><p>

  406.          Disable the thread-safety of client libraries.  This prevents

  407.          concurrent threads in <span class="application">libpq</span> and

  408.          <span class="application">ECPG</span> programs from safely controlling

  409.          their private connection handles.

  410.         </p></dd><dt><span class="term"><code class="option">--with-system-tzdata=<em class="replaceable"><code>DIRECTORY</code></em></code>

  411.        <a id="id-1.6.3.8.2.1.6.1.33.1.2" class="indexterm"></a>

  412.        </span></dt><dd><p>

  413.          <span class="productname">PostgreSQL</span> includes its own time zone database,

  414.          which it requires for date and time operations.  This time zone

  415.          database is in fact compatible with the IANA time zone

  416.          database provided by many operating systems such as FreeBSD,

  417.          Linux, and Solaris, so it would be redundant to install it again.

  418.          When this option is used, the system-supplied time zone database

  419.          in <em class="replaceable"><code>DIRECTORY</code></em> is used instead of the one

  420.          included in the PostgreSQL source distribution.

  421.          <em class="replaceable"><code>DIRECTORY</code></em> must be specified as an

  422.          absolute path.  <code class="filename">/usr/share/zoneinfo</code> is a

  423.          likely directory on some operating systems.  Note that the

  424.          installation routine will not detect mismatching or erroneous time

  425.          zone data.  If you use this option, you are advised to run the

  426.          regression tests to verify that the time zone data you have

  427.          pointed to works correctly with <span class="productname">PostgreSQL</span>.

  428.         </p><a id="id-1.6.3.8.2.1.6.1.33.2.2" class="indexterm"></a><p>

  429.          This option is mainly aimed at binary package distributors

  430.          who know their target operating system well.  The main

  431.          advantage of using this option is that the PostgreSQL package

  432.          won't need to be upgraded whenever any of the many local

  433.          daylight-saving time rules change.  Another advantage is that

  434.          PostgreSQL can be cross-compiled more straightforwardly if the

  435.          time zone database files do not need to be built during the

  436.          installation.

  437.         </p></dd><dt><span class="term"><code class="option">--without-zlib</code></span></dt><dd><p>

  438.          <a id="id-1.6.3.8.2.1.6.1.34.2.1.1" class="indexterm"></a>

  439.          Prevents use of the <span class="application">Zlib</span> library.  This disables

  440.          support for compressed archives in <span class="application">pg_dump</span>

  441.          and <span class="application">pg_restore</span>.

  442.          This option is only intended for those rare systems where this

  443.          library is not available.

  444.         </p></dd><dt><span class="term"><code class="option">--enable-debug</code></span></dt><dd><p>

  445.          Compiles all programs and libraries with debugging symbols.

  446.          This means that you can run the programs in a debugger

  447.          to analyze problems. This enlarges the size of the installed

  448.          executables considerably, and on non-GCC compilers it usually

  449.          also disables compiler optimization, causing slowdowns. However,

  450.          having the symbols available is extremely helpful for dealing

  451.          with any problems that might arise.  Currently, this option is

  452.          recommended for production installations only if you use GCC.

  453.          But you should always have it on if you are doing development work

  454.          or running a beta version.

  455.         </p></dd><dt><span class="term"><code class="option">--enable-coverage</code></span></dt><dd><p>

  456.          If using GCC, all programs and libraries are compiled with

  457.          code coverage testing instrumentation.  When run, they

  458.          generate files in the build directory with code coverage

  459.          metrics.

  460.          <span class="phrase">See <a class="xref" href="regress-coverage.html" title="32.5. Test Coverage Examination">Section 32.5</a>

  461.          for more information.</span> This option is for use only with GCC

  462.          and when doing development work.

  463.         </p></dd><dt><span class="term"><code class="option">--enable-profiling</code></span></dt><dd><p>

  464.          If using GCC, all programs and libraries are compiled so they

  465.          can be profiled.  On backend exit, a subdirectory will be created

  466.          that contains the <code class="filename">gmon.out</code> file for use in profiling.

  467.          This option is for use only with GCC and when doing development work.

  468.         </p></dd><dt><span class="term"><code class="option">--enable-cassert</code></span></dt><dd><p>

  469.          Enables <em class="firstterm">assertion</em> checks in the server, which test for

  470.          many <span class="quote">“<span class="quote">cannot happen</span>”</span> conditions.  This is invaluable for

  471.          code development purposes, but the tests can slow down the

  472.          server significantly.

  473.          Also, having the tests turned on won't necessarily enhance the

  474.          stability of your server!  The assertion checks are not categorized

  475.          for severity, and so what might be a relatively harmless bug will

  476.          still lead to server restarts if it triggers an assertion

  477.          failure.  This option is not recommended for production use, but

  478.          you should have it on for development work or when running a beta

  479.          version.

  480.         </p></dd><dt><span class="term"><code class="option">--enable-depend</code></span></dt><dd><p>

  481.          Enables automatic dependency tracking.  With this option, the

  482.          makefiles are set up so that all affected object files will

  483.          be rebuilt when any header file is changed.  This is useful

  484.          if you are doing development work, but is just wasted overhead

  485.          if you intend only to compile once and install.  At present,

  486.          this option only works with GCC.

  487.         </p></dd><dt><span class="term"><code class="option">--enable-dtrace</code></span></dt><dd><p>

  488.          <a id="id-1.6.3.8.2.1.6.1.40.2.1.1" class="indexterm"></a>

  489.          Compiles <span class="productname">PostgreSQL</span> with support for the

  490.          dynamic tracing tool DTrace.

  491.          <span class="phrase">See <a class="xref" href="dynamic-trace.html" title="27.5. Dynamic Tracing">Section 27.5</a>

  492.          for more information.</span>

  493.         </p><p>

  494.          To point to the <code class="command">dtrace</code> program, the

  495.          environment variable <code class="envar">DTRACE</code> can be set.  This

  496.          will often be necessary because <code class="command">dtrace</code> is

  497.          typically installed under <code class="filename">/usr/sbin</code>,

  498.          which might not be in the path.

  499.         </p><p>

  500.          Extra command-line options for the <code class="command">dtrace</code> program

  501.          can be specified in the environment variable

  502.          <code class="envar">DTRACEFLAGS</code>.  On Solaris,

  503.          to include DTrace support in a 64-bit binary, you must specify

  504.          <code class="literal">DTRACEFLAGS="-64"</code> to configure.  For example,

  505.          using the GCC compiler:

  506. </p><pre class="screen">

  507. ./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ...

  508. </pre><p>

  509.          Using Sun's compiler:

  510. </p><pre class="screen">

  511. ./configure CC='/opt/SUNWspro/bin/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64' ...

  512. </pre><p>

  513.         </p></dd><dt><span class="term"><code class="option">--enable-tap-tests</code></span></dt><dd><p>

  514.          Enable tests using the Perl TAP tools.  This requires a Perl

  515.          installation and the Perl module <code class="literal">IPC::Run</code>.

  516.          <span class="phrase">See <a class="xref" href="regress-tap.html" title="32.4. TAP Tests">Section 32.4</a> for more information.</span>

  517.         </p></dd></dl></div><p>

  518.     </p><p>

  519.      If you prefer a C compiler different from the one

  520.      <code class="filename">configure</code> picks, you can set the

  521.      environment variable <code class="envar">CC</code> to the program of your choice.

  522.      By default, <code class="filename">configure</code> will pick

  523.      <code class="filename">gcc</code> if available, else the platform's

  524.      default (usually <code class="filename">cc</code>).  Similarly, you can override the

  525.      default compiler flags if needed with the <code class="envar">CFLAGS</code> variable.

  526.     </p><p>

  527.      You can specify environment variables on the

  528.      <code class="filename">configure</code> command line, for example:

  529. </p><pre class="screen">

  530. <strong class="userinput"><code>./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'</code></strong>

  531. </pre><p>

  532.     </p><p>

  533.      Here is a list of the significant variables that can be set in

  534.      this manner:

  535. 

  536.      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="envar">BISON</code></span></dt><dd><p>

  537.          Bison program

  538.         </p></dd><dt><span class="term"><code class="envar">CC</code></span></dt><dd><p>

  539.          C compiler

  540.         </p></dd><dt><span class="term"><code class="envar">CFLAGS</code></span></dt><dd><p>

  541.          options to pass to the C compiler

  542.         </p></dd><dt><span class="term"><code class="envar">CLANG</code></span></dt><dd><p>

  543.          path to <code class="command">clang</code> program used to process source code

  544.          for inlining when compiling with <code class="literal">--with-llvm</code>

  545.         </p></dd><dt><span class="term"><code class="envar">CPP</code></span></dt><dd><p>

  546.          C preprocessor

  547.         </p></dd><dt><span class="term"><code class="envar">CPPFLAGS</code></span></dt><dd><p>

  548.          options to pass to the C preprocessor

  549.         </p></dd><dt><span class="term"><code class="envar">CXX</code></span></dt><dd><p>

  550.          C++ compiler

  551.         </p></dd><dt><span class="term"><code class="envar">CXXFLAGS</code></span></dt><dd><p>

  552.          options to pass to the C++ compiler

  553.         </p></dd><dt><span class="term"><code class="envar">DTRACE</code></span></dt><dd><p>

  554.          location of the <code class="command">dtrace</code> program

  555.         </p></dd><dt><span class="term"><code class="envar">DTRACEFLAGS</code></span></dt><dd><p>

  556.          options to pass to the <code class="command">dtrace</code> program

  557.         </p></dd><dt><span class="term"><code class="envar">FLEX</code></span></dt><dd><p>

  558.          Flex program

  559.         </p></dd><dt><span class="term"><code class="envar">LDFLAGS</code></span></dt><dd><p>

  560.          options to use when linking either executables or shared libraries

  561.         </p></dd><dt><span class="term"><code class="envar">LDFLAGS_EX</code></span></dt><dd><p>

  562.          additional options for linking executables only

  563.         </p></dd><dt><span class="term"><code class="envar">LDFLAGS_SL</code></span></dt><dd><p>

  564.          additional options for linking shared libraries only

  565.         </p></dd><dt><span class="term"><code class="envar">LLVM_CONFIG</code></span></dt><dd><p>

  566.          <code class="command">llvm-config</code> program used to locate the

  567.          <span class="productname">LLVM</span> installation.

  568.         </p></dd><dt><span class="term"><code class="envar">MSGFMT</code></span></dt><dd><p>

  569.          <code class="command">msgfmt</code> program for native language support

  570.         </p></dd><dt><span class="term"><code class="envar">PERL</code></span></dt><dd><p>

  571.          Perl interpreter program.  This will be used to determine the

  572.          dependencies for building PL/Perl.  The default is

  573.          <code class="command">perl</code>.

  574.         </p></dd><dt><span class="term"><code class="envar">PYTHON</code></span></dt><dd><p>

  575.          Python interpreter program.  This will be used to

  576.          determine the dependencies for building PL/Python.  Also,

  577.          whether Python 2 or 3 is specified here (or otherwise

  578.          implicitly chosen) determines which variant of the PL/Python

  579.          language becomes available.  See

  580.          <a class="xref" href="plpython-python23.html" title="45.1. Python 2 vs. Python 3">Section 45.1</a>

  581.          for more information.  If this is not set, the following are probed

  582.          in this order: <code class="literal">python python3 python2</code>.

  583.         </p></dd><dt><span class="term"><code class="envar">TCLSH</code></span></dt><dd><p>

  584.          Tcl interpreter program.  This will be used to

  585.          determine the dependencies for building PL/Tcl, and it will

  586.          be substituted into Tcl scripts.

  587.         </p></dd><dt><span class="term"><code class="envar">XML2_CONFIG</code></span></dt><dd><p>

  588.          <code class="command">xml2-config</code> program used to locate the

  589.          libxml2 installation

  590.         </p></dd></dl></div><p>

  591.     </p><p>

  592.      Sometimes it is useful to add compiler flags after-the-fact to the set

  593.      that were chosen by <code class="filename">configure</code>.  An important example is

  594.      that <span class="application">gcc</span>'s <code class="option">-Werror</code> option cannot be included

  595.      in the <code class="envar">CFLAGS</code> passed to <code class="filename">configure</code>, because

  596.      it will break many of <code class="filename">configure</code>'s built-in tests.  To add

  597.      such flags, include them in the <code class="envar">COPT</code> environment variable

  598.      while running <code class="filename">make</code>.  The contents of <code class="envar">COPT</code>

  599.      are added to both the <code class="envar">CFLAGS</code> and <code class="envar">LDFLAGS</code>

  600.      options set up by <code class="filename">configure</code>.  For example, you could do

  601. </p><pre class="screen">

  602. <strong class="userinput"><code>make COPT='-Werror'</code></strong>

  603. </pre><p>

  604.      or

  605. </p><pre class="screen">

  606. <strong class="userinput"><code>export COPT='-Werror'</code></strong>

  607. <strong class="userinput"><code>make</code></strong>

  608. </pre><p>

  609.     </p><div class="note"><h3 class="title">Note</h3><p>

  610.       When developing code inside the server, it is recommended to

  611.       use the configure options <code class="option">--enable-cassert</code> (which

  612.       turns on many run-time error checks) and <code class="option">--enable-debug</code>

  613.       (which improves the usefulness of debugging tools).

  614.      </p><p>

  615.       If using GCC, it is best to build with an optimization level of

  616.       at least <code class="option">-O1</code>, because using no optimization

  617.       (<code class="option">-O0</code>) disables some important compiler warnings (such

  618.       as the use of uninitialized variables).  However, non-zero

  619.       optimization levels can complicate debugging because stepping

  620.       through compiled code will usually not match up one-to-one with

  621.       source code lines.  If you get confused while trying to debug

  622.       optimized code, recompile the specific files of interest with

  623.       <code class="option">-O0</code>.  An easy way to do this is by passing an option

  624.       to <span class="application">make</span>: <code class="command">make PROFILE=-O0 file.o</code>.

  625.      </p><p>

  626.       The <code class="envar">COPT</code> and <code class="envar">PROFILE</code> environment variables are

  627.       actually handled identically by the <span class="productname">PostgreSQL</span>

  628.       makefiles.  Which to use is a matter of preference, but a common habit

  629.       among developers is to use <code class="envar">PROFILE</code> for one-time flag

  630.       adjustments, while <code class="envar">COPT</code> might be kept set all the time.

  631.      </p></div></li><li class="step" id="BUILD"><p class="title"><strong>Build</strong></p><p>

  632.     To start the build, type either of:

  633. </p><pre class="screen">

  634. <strong class="userinput"><code>make</code></strong>

  635. <strong class="userinput"><code>make all</code></strong>

  636. </pre><p>

  637.     (Remember to use <acronym class="acronym">GNU</acronym> <span class="application">make</span>.)

  638.     The build will take a few minutes depending on your

  639.     hardware. The last line displayed should be:

  640. </p><pre class="screen">

  641. All of PostgreSQL successfully made. Ready to install.

  642. </pre><p>

  643.    </p><p>

  644.    If you want to build everything that can be built, including the

  645.    documentation (HTML and man pages), and the additional modules

  646.    (<code class="filename">contrib</code>), type instead:

  647. </p><pre class="screen">

  648. <strong class="userinput"><code>make world</code></strong>

  649. </pre><p>

  650.    The last line displayed should be:

  651. </p><pre class="screen">

  652. PostgreSQL, contrib, and documentation successfully made. Ready to install.

  653. </pre><p>

  654.    </p><p>

  655.     If you want to invoke the build from another makefile rather than

  656.     manually, you must unset <code class="varname">MAKELEVEL</code> or set it to zero,

  657.     for instance like this:

  658. </p><pre class="programlisting">

  659. build-postgresql:

  660.         $(MAKE) -C postgresql MAKELEVEL=0 all

  661. </pre><p>

  662.     Failure to do that can lead to strange error messages, typically about

  663.     missing header files.

  664.    </p></li><li class="step"><p class="title"><strong>Regression Tests</strong></p><a id="id-1.6.3.8.2.3.2" class="indexterm"></a><p>

  665.     If you want to test the newly built server before you install it,

  666.     you can run the regression tests at this point. The regression

  667.     tests are a test suite to verify that <span class="productname">PostgreSQL</span>

  668.     runs on your machine in the way the developers expected it

  669.     to. Type:

  670. </p><pre class="screen">

  671. <strong class="userinput"><code>make check</code></strong>

  672. </pre><p>

  673.     (This won't work as root; do it as an unprivileged user.)

  674.     See <a class="xref" href="regress.html" title="Chapter 32. Regression Tests">Chapter 32</a> for

  675.     detailed information about interpreting the test results. You can

  676.     repeat this test at any later time by issuing the same command.

  677.    </p></li><li class="step" id="INSTALL"><p class="title"><strong>Installing the Files</strong></p><div class="note"><h3 class="title">Note</h3><p>

  678.      If you are upgrading an existing system be sure to read

  679.      <a class="xref" href="upgrading.html" title="18.6. Upgrading a PostgreSQL Cluster">Section 18.6</a>,

  680.      which has instructions about upgrading a

  681.      cluster.

  682.     </p></div><p>

  683.     To install <span class="productname">PostgreSQL</span> enter:

  684. </p><pre class="screen">

  685. <strong class="userinput"><code>make install</code></strong>

  686. </pre><p>

  687.     This will install files into the directories that were specified

  688.     in <a class="xref" href="install-procedure.html#CONFIGURE" title="Configuration">Step 1</a>. Make sure that you have appropriate

  689.     permissions to write into that area. Normally you need to do this

  690.     step as root. Alternatively, you can create the target

  691.     directories in advance and arrange for appropriate permissions to

  692.     be granted.

  693.    </p><p>

  694.     To install the documentation (HTML and man pages), enter:

  695. </p><pre class="screen">

  696. <strong class="userinput"><code>make install-docs</code></strong>

  697. </pre><p>

  698.    </p><p>

  699.     If you built the world above, type instead:

  700. </p><pre class="screen">

  701. <strong class="userinput"><code>make install-world</code></strong>

  702. </pre><p>

  703.     This also installs the documentation.

  704.    </p><p>

  705.     You can use <code class="literal">make install-strip</code> instead of

  706.     <code class="literal">make install</code> to strip the executable files and

  707.     libraries as they are installed.  This will save some space.  If

  708.     you built with debugging support, stripping will effectively

  709.     remove the debugging support, so it should only be done if

  710.     debugging is no longer needed.  <code class="literal">install-strip</code>

  711.     tries to do a reasonable job saving space, but it does not have

  712.     perfect knowledge of how to strip every unneeded byte from an

  713.     executable file, so if you want to save all the disk space you

  714.     possibly can, you will have to do manual work.

  715.    </p><p>

  716.     The standard installation provides all the header files needed for client

  717.     application development as well as for server-side program

  718.     development, such as custom functions or data types written in C.

  719.     (Prior to <span class="productname">PostgreSQL</span> 8.0, a separate <code class="literal">make

  720.     install-all-headers</code> command was needed for the latter, but this

  721.     step has been folded into the standard install.)

  722.    </p><p><strong>Client-only installation: </strong>

  723.      If you want to install only the client applications and

  724.      interface libraries, then you can use these commands:

  725. </p><pre class="screen">

  726. <strong class="userinput"><code>make -C src/bin install</code></strong>

  727. <strong class="userinput"><code>make -C src/include install</code></strong>

  728. <strong class="userinput"><code>make -C src/interfaces install</code></strong>

  729. <strong class="userinput"><code>make -C doc install</code></strong>

  730. </pre><p>

  731.     <code class="filename">src/bin</code> has a few binaries for server-only use,

  732.     but they are small.

  733.     </p></li></ol></div><p><strong>Uninstallation: </strong>

  734.     To undo the installation use the command <code class="command">make

  735.     uninstall</code>. However, this will not remove any created directories.

  736.    </p><p><strong>Cleaning: </strong>

  737.     After the installation you can free disk space by removing the built

  738.     files from the source tree with the command <code class="command">make

  739.     clean</code>. This will preserve the files made by the <code class="command">configure</code>

  740.     program, so that you can rebuild everything with <code class="command">make</code>

  741.     later on. To reset the source tree to the state in which it was

  742.     distributed, use <code class="command">make distclean</code>. If you are going to

  743.     build for several platforms within the same source tree you must do

  744.     this and re-configure for each platform.  (Alternatively, use

  745.     a separate build tree for each platform, so that the source tree

  746.     remains unmodified.)

  747.    </p><p>

  748.    If you perform a build and then discover that your <code class="command">configure</code>

  749.    options were wrong, or if you change anything that <code class="command">configure</code>

  750.    investigates (for example, software upgrades), then it's a good

  751.    idea to do <code class="command">make distclean</code> before reconfiguring and

  752.    rebuilding.  Without this, your changes in configuration choices

  753.    might not propagate everywhere they need to.

  754.   </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-getsource.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installation.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="install-post.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">16.3. Getting the Source </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 16.5. Post-Installation Setup</td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1