~ubuntu-branches/debian/experimental/postgresql-11/experimental

<!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.2. Requirements</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="install-short.html" title="16.1. Short Version" /><link rel="next" href="install-getsource.html" title="16.3. Getting The Source" /></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.2. Requirements</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="install-short.html" title="16.1. Short Version">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 11beta1 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="install-getsource.html" title="16.3. Getting The Source">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="INSTALL-REQUIREMENTS"><div class="titlepage"><div><div><h2 class="title" style="clear: both">16.2. Requirements</h2></div></div></div>

In general, a modern Unix-compatible platform should be able to run

PostgreSQL.

The platforms that had received specific testing at the

time of release are listed in <a class="xref" href="supported-platforms.html" title="16.6. Supported Platforms">Section 16.6</a>

below. In the <code class="filename">doc</code> subdirectory of the distribution

there are several platform-specific <acronym class="acronym">FAQ</acronym> documents you

might wish to consult if you are having trouble.

The following software packages are required for building

PostgreSQL:

<acronym class="acronym">GNU</acronym> make version 3.80 or newer is required; other

make programs or older <acronym class="acronym">GNU</acronym> make versions will not work.

(<acronym class="acronym">GNU</acronym> make is sometimes installed under

the name <code class="filename">gmake</code>.) To test for <acronym class="acronym">GNU</acronym>

make enter:

<code>make --version</code>

</pre>

</li><li class="listitem">

You need an <acronym class="acronym">ISO</acronym>/<acronym class="acronym">ANSI</acronym> C compiler (at least

C89-compliant). Recent

versions of GCC are recommended, but

PostgreSQL is known to build using a wide variety

of compilers from different vendors.

</li><li class="listitem">

tar is required to unpack the source

distribution, in addition to either

gzip or bzip2.

</li><li class="listitem">

The <acronym class="acronym">GNU</acronym> Readline library is used by

default. It allows psql (the

PostgreSQL command line SQL interpreter) to remember each

command you type, and allows you to use arrow keys to recall and

edit previous commands. This is very helpful and is strongly

recommended. If you don't want to use it then you must specify

the <code class="option">--without-readline</code> option to

<code class="filename">configure</code>. As an alternative, you can often use the

BSD-licensed <code class="filename">libedit</code> library, originally

developed on NetBSD. The

<code class="filename">libedit</code> library is

GNU Readline-compatible and is used if

<code class="filename">libreadline</code> is not found, or if

<code class="option">--with-libedit-preferred</code> is used as an

option to <code class="filename">configure</code>. If you are using a package-based

Linux distribution, be aware that you need both the

<code class="literal">readline</code> and <code class="literal">readline-devel</code> packages, if

those are separate in your distribution.

</li><li class="listitem">

The zlib compression library is

used by default. If you don't want to use it then you must

specify the <code class="option">--without-zlib</code> option to

<code class="filename">configure</code>. Using this option disables

support for compressed archives in pg_dump and

pg_restore.

</li></ul></div>

The following packages are optional. They are not required in the

default configuration, but they are needed when certain build

options are enabled, as explained below:

To build the server programming language

PL/Perl you need a full

Perl installation, including the

<code class="filename">libperl</code> library and the header files.

The minimum required version is Perl 5.8.3.

Since PL/Perl will be a shared

library, the <a id="id-1.6.3.5.4.1.1.1.6" class="indexterm"></a>

<code class="filename">libperl</code> library must be a shared library

also on most platforms. This appears to be the default in

recent Perl versions, but it was not

in earlier versions, and in any case it is the choice of whomever

installed Perl at your site. <code class="filename">configure</code> will fail

if building PL/Perl is selected but it cannot

find a shared <code class="filename">libperl</code>. In that case, you will have

to rebuild and install Perl manually to be

able to build PL/Perl. During the

configuration process for Perl, request a

shared library.

If you intend to make more than incidental use of

PL/Perl, you should ensure that the

Perl installation was built with the

<code class="literal">usemultiplicity</code> option enabled (<code class="literal">perl -V</code>

will show whether this is the case).

</li><li class="listitem">

To build the PL/Python server programming

language, you need a Python

100

installation with the header files and

101

the distutils module. The minimum

102

required version is Python 2.4.

103

Python 3 is supported if it's

104

version 3.1 or later; but see

105

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

106

when using Python 3.

107

108

Since PL/Python will be a shared

109

library, the <a id="id-1.6.3.5.4.1.2.2.2" class="indexterm"></a>

110

<code class="filename">libpython</code> library must be a shared library

111

also on most platforms. This is not the case in a default

112

Python installation built from source, but a

113

shared library is available in many operating system

114

distributions. <code class="filename">configure</code> will fail if

115

building PL/Python is selected but it cannot

116

find a shared <code class="filename">libpython</code>. That might mean that you

117

either have to install additional packages or rebuild (part of) your

118

Python installation to provide this shared

119

library. When building from source, run Python's

120

configure with the <code class="literal">--enable-shared</code> flag.

121

</li><li class="listitem">

122

To build the PL/Tcl

123

procedural language, you of course need a Tcl

124

installation. The minimum required version is

125

Tcl 8.4.

126

</li><li class="listitem">

127

To enable Native Language Support (<acronym class="acronym">NLS</acronym>), that

128

is, the ability to display a program's messages in a language

129

other than English, you need an implementation of the

130

Gettext <acronym class="acronym">API</acronym>. Some operating

131

systems have this built-in (e.g., Linux, NetBSD,

132

Solaris), for other systems you

133

can download an add-on package from <a class="ulink" href="http://www.gnu.org/software/gettext/" target="_top">http://www.gnu.org/software/gettext/</a>.

134

If you are using the Gettext implementation in

135

the <acronym class="acronym">GNU</acronym> C library then you will additionally

136

need the GNU Gettext package for some

137

utility programs. For any of the other implementations you will

138

not need it.

139

</li><li class="listitem">

140

You need OpenSSL, if you want to support

141

encrypted client connections. The minimum required version is

142

0.9.8.

143

</li><li class="listitem">

144

You need Kerberos, OpenLDAP,

145

and/or PAM, if you want to support authentication

146

using those services.

147

</li><li class="listitem">

148

To build the PostgreSQL documentation,

149

there is a separate set of requirements; see

150

<a class="xref" href="docguide-toolsets.html" title="J.2. Tool Sets">Section J.2</a>.

151

</li></ul></div>

152

153

If you are building from a Git tree instead of

154

using a released source package, or if you want to do server development,

155

you also need the following packages:

156

157

158

159

160

161

162

163

Flex and Bison

164

are needed to build from a Git checkout, or if you changed the actual

165

scanner and parser definition files. If you need them, be sure

166

to get Flex 2.5.31 or later and

167

Bison 1.875 or later. Other lex

168

and yacc programs cannot be used.

169

</li><li class="listitem">

170

171

172

Perl 5.8.3 or later is needed to build from a Git checkout,

173

or if you changed the input files for any of the build steps that

174

use Perl scripts. If building on Windows you will need

175

Perl in any case. Perl is

176

also required to run some test suites.

177

</li></ul></div>

178

179

If you need to get a <acronym class="acronym">GNU</acronym> package, you can find

180

it at your local <acronym class="acronym">GNU</acronym> mirror site (see <a class="ulink" href="http://www.gnu.org/order/ftp.html" target="_top">http://www.gnu.org/order/ftp.html</a>

181

for a list) or at <a class="ulink" href="ftp://ftp.gnu.org/gnu/" target="_top">ftp://ftp.gnu.org/gnu/</a>.

182

183

Also check that you have sufficient disk space. You will need about

184

100 MB for the source tree during compilation and about 20 MB for

185

the installation directory. An empty database cluster takes about

186

35 MB; databases take about five times the amount of space that a

187

flat text file with the same data would take. If you are going to

188

run the regression tests you will temporarily need up to an extra

189

150 MB. Use the <code class="command">df</code> command to check free disk

190

space.

191

</div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-short.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-getsource.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">16.1. Short Version </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 16.3. Getting The Source</td></tr></table></div></body></html>

b'\\ No newline at end of file'

Older »