PostgreSQL

  +
  LLVM support requires a compatible `+clang+` compiler (specified, if necessary, using the `+CLANG+` environment variable), and a working C++ compiler (specified, if necessary, using the `+CXX+` environment variable).
[.term]#`+--with-icu+`#::
  Build with support for the ICU library. This requires the ICU4C package to be installed. The minimum required version of ICU4C is currently 4.2.
  +
  By default, pkg-config will be used to find the required compilation options. This is supported for ICU4C version 4.6 and later. For older versions, or if pkg-config is not available, the variables `+ICU_CFLAGS+` and `+ICU_LIBS+` can be specified to `+configure+`, like in this example:
  +

  +
  (If ICU4C is in the default search path for the compiler, then you still need to specify a nonempty string in order to avoid use of pkg-config, for example, `+ICU_CFLAGS=' '+`.)
[.term]#`+--with-openssl+` ::
  Build with support for SSL (encrypted) connections. This requires the OpenSSL package to be installed. `+configure+` will check for the required header files and libraries to make sure that your OpenSSL installation is sufficient before proceeding.
[.term]#`+--with-pam+`#::
  Build with PAM (Pluggable Authentication Modules) support.
[.term]#`+--with-bsd-auth+`#::
  Build with BSD Authentication support. (The BSD Authentication framework is currently only available on OpenBSD.)
[.term]#`+--with-ldap+`#::
  Build with LDAP support for authentication and connection parameter lookup (see [#INSTALL-LDAP-LINKS .phrase]#link:libpq-ldap.html[Section 33.17] and link:auth-ldap.html[Section 20.10]# for more information). On Unix, this requires the OpenLDAP package to be installed. On Windows, the default WinLDAP library is used. `+configure+` will check for the required header files and libraries to make sure that your OpenLDAP installation is sufficient before proceeding.
[.term]#`+--with-systemd+`#::
  Build with support for systemd service notifications. This improves integration if the server binary is started under systemd but has no impact otherwise[[phrase]]; see link:server-start.html[Section 18.3] for more information##. libsystemd and the associated header files need to be installed to be able to use this option.
[.term]#`+--without-readline+`#::
  Prevents use of the Readline library (and libedit as well). This option disables command-line editing and history in psql, so it is not recommended.
[.term]#`+--with-libedit-preferred+`#::
  Favors the use of the BSD-licensed libedit library rather than GPL-licensed Readline. This option is significant only if you have both libraries installed; the default in that case is to use Readline.
[.term]#`+--with-bonjour+`#::
  Build with Bonjour support. This requires Bonjour support in your operating system. Recommended on macOS.
[.term]#`+--with-uuid=+`_`+LIBRARY+`_#::
  Build the link:uuid-ossp.html[uuid-ossp] module (which provides functions to generate UUIDs), using the specified UUID library. _`+LIBRARY+`_ must be one of:
  +
  * `+bsd+` to use the UUID functions found in FreeBSD and some other BSD-derived systems
  * `+e2fs+` to use the UUID library created by the `+e2fsprogs+` project; this library is present in most Linux systems and in macOS, and can be obtained for other platforms as well
  * `+ossp+` to use the http://www.ossp.org/pkg/lib/uuid/[OSSP UUID library]
[.term]#`+--with-ossp-uuid+`#::
  Obsolete equivalent of `+--with-uuid=ossp+`.
[.term]#`+--with-libxml+`#::
  Build with libxml2, enabling SQL/XML support. Libxml2 version 2.6.23 or later is required for this feature.
  +
  To detect the required compiler and linker options, PostgreSQL will query `+pkg-config+`, if that is installed and knows about libxml2. Otherwise the program `+xml2-config+`, which is installed by libxml2, will be used if it is found. Use of `+pkg-config+` is preferred, because it can deal with multi-architecture installations better.
  +
  To use a libxml2 installation that is in an unusual location, you can set `+pkg-config+`-related environment variables (see its documentation), or set the environment variable `+XML2_CONFIG+` to point to the `+xml2-config+` program belonging to the libxml2 installation, or set the variables `+XML2_CFLAGS+` and `+XML2_LIBS+`. (If `+pkg-config+` is installed, then to override its idea of where libxml2 is you must either set `+XML2_CONFIG+` or set both `+XML2_CFLAGS+` and `+XML2_LIBS+` to nonempty strings.)
[.term]#`+--with-libxslt+`#::
  Use libxslt when building the link:xml2.html[xml2] module. xml2 relies on this library to perform XSL transformations of XML.
[.term]#`+--disable-float4-byval+`#::
  Disable passing float4 values [.quote]#“[.quote]#by value#”#, causing them to be passed [.quote]#“[.quote]#by reference#”# instead. This option costs performance, but may be needed for compatibility with old user-defined functions that are written in C and use the [.quote]#“[.quote]#version 0#”# calling convention. A better long-term solution is to update any such functions to use the [.quote]#“[.quote]#version 1#”# calling convention.
[.term]#`+--disable-float8-byval+`#::
  Disable passing float8 values [.quote]#“[.quote]#by value#”#, causing them to be passed [.quote]#“[.quote]#by reference#”# instead. This option costs performance, but may be needed for compatibility with old user-defined functions that are written in C and use the [.quote]#“[.quote]#version 0#”# calling convention. A better long-term solution is to update any such functions to use the [.quote]#“[.quote]#version 1#”# calling convention. Note that this option affects not only float8, but also int8 and some related types such as timestamp. On 32-bit platforms, `+--disable-float8-byval+` is the default and it is not allowed to select `+--enable-float8-byval+`.
[.term]#`+--with-segsize=+`_`+SEGSIZE+`_#::
  Set the _segment size_, in gigabytes. Large tables are divided into multiple operating-system files, each of size equal to the segment size. This avoids problems with file size limits that exist on many platforms. The default segment size, 1 gigabyte, is safe on all supported platforms. If your operating system has [.quote]#“[.quote]#largefile#”# support (which most do, nowadays), you can use a larger segment size. This can be helpful to reduce the number of file descriptors consumed when working with very large tables. But be careful not to select a value larger than is supported by your platform and the file systems you intend to use. Other tools you might wish to use, such as tar, could also set limits on the usable file size. It is recommended, though not absolutely required, that this value be a power of 2. Note that changing this value requires an initdb.
[.term]#`+--with-blocksize=+`_`+BLOCKSIZE+`_#::
  Set the _block size_, in kilobytes. This is the unit of storage and I/O within tables. The default, 8 kilobytes, is suitable for most situations; but other values may be useful in special cases. The value must be a power of 2 between 1 and 32 (kilobytes). Note that changing this value requires an initdb.
[.term]#`+--with-wal-blocksize=+`_`+BLOCKSIZE+`_#::
  Set the _WAL block size_, in kilobytes. This is the unit of storage and I/O within the WAL log. The default, 8 kilobytes, is suitable for most situations; but other values may be useful in special cases. The value must be a power of 2 between 1 and 64 (kilobytes). Note that changing this value requires an initdb.
[.term]#`+--disable-spinlocks+`#::
  Allow the build to succeed even if PostgreSQL has no CPU spinlock support for the platform. The lack of spinlock support will result in poor performance; therefore, this option should only be used if the build aborts and informs you that the platform lacks spinlock support. If this option is required to build PostgreSQL on your platform, please report the problem to the PostgreSQL developers.
[.term]#`+--disable-thread-safety+`#::
  Disable the thread-safety of client libraries. This prevents concurrent threads in libpq and ECPG programs from safely controlling their private connection handles.
[.term]#`+--with-system-tzdata=+`_`+DIRECTORY+`_ ::
  PostgreSQL includes its own time zone database, which it requires for date and time operations. This time zone database is in fact compatible with the IANA time zone database provided by many operating systems such as FreeBSD, Linux, and Solaris, so it would be redundant to install it again. When this option is used, the system-supplied time zone database in _`+DIRECTORY+`_ is used instead of the one included in the PostgreSQL source distribution. _`+DIRECTORY+`_ must be specified as an absolute path. `+/usr/share/zoneinfo+` is a likely directory on some operating systems. Note that the installation routine will not detect mismatching or erroneous time zone data. If you use this option, you are advised to run the regression tests to verify that the time zone data you have pointed to works correctly with PostgreSQL.
  +

  +
  This option is mainly aimed at binary package distributors who know their target operating system well. The main advantage of using this option is that the PostgreSQL package won't need to be upgraded whenever any of the many local daylight-saving time rules change. Another advantage is that PostgreSQL can be cross-compiled more straightforwardly if the time zone database files do not need to be built during the installation.
[.term]#`+--without-zlib+`#::
   Prevents use of the Zlib library. This disables support for compressed archives in pg_dump and pg_restore. This option is only intended for those rare systems where this library is not available.
[.term]#`+--enable-debug+`#::
  Compiles all programs and libraries with debugging symbols. This means that you can run the programs in a debugger to analyze problems. This enlarges the size of the installed executables considerably, and on non-GCC compilers it usually also disables compiler optimization, causing slowdowns. However, having the symbols available is extremely helpful for dealing with any problems that might arise. Currently, this option is recommended for production installations only if you use GCC. But you should always have it on if you are doing development work or running a beta version.
[.term]#`+--enable-coverage+`#::
  If using GCC, all programs and libraries are compiled with code coverage testing instrumentation. When run, they generate files in the build directory with code coverage metrics. [.phrase]#See link:regress-coverage.html[Section 32.5] for more information.# This option is for use only with GCC and when doing development work.
[.term]#`+--enable-profiling+`#::
  If using GCC, all programs and libraries are compiled so they can be profiled. On backend exit, a subdirectory will be created that contains the `+gmon.out+` file for use in profiling. This option is for use only with GCC and when doing development work.
[.term]#`+--enable-cassert+`#::
  Enables _assertion_ checks in the server, which test for many [.quote]#“[.quote]#cannot happen#”# conditions. This is invaluable for code development purposes, but the tests can slow down the server significantly. Also, having the tests turned on won't necessarily enhance the stability of your server! The assertion checks are not categorized for severity, and so what might be a relatively harmless bug will still lead to server restarts if it triggers an assertion failure. This option is not recommended for production use, but you should have it on for development work or when running a beta version.
[.term]#`+--enable-depend+`#::
  Enables automatic dependency tracking. With this option, the makefiles are set up so that all affected object files will be rebuilt when any header file is changed. This is useful if you are doing development work, but is just wasted overhead if you intend only to compile once and install. At present, this option only works with GCC.
[.term]#`+--enable-dtrace+`#::
   Compiles PostgreSQL with support for the dynamic tracing tool DTrace. [.phrase]#See link:dynamic-trace.html[Section 27.5] for more information.#
  +
  To point to the `+dtrace+` program, the environment variable `+DTRACE+` can be set. This will often be necessary because `+dtrace+` is typically installed under `+/usr/sbin+`, which might not be in the path.
  +
  Extra command-line options for the `+dtrace+` program can be specified in the environment variable `+DTRACEFLAGS+`. On Solaris, to include DTrace support in a 64-bit binary, you must specify `+DTRACEFLAGS="-64"+` to configure. For example, using the GCC compiler:
  +

+
Using Sun's compiler:
+