Skip to content

P
Postgres FD Implementation
Commit 5ba1fab5 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update INSTALL file for 7.4.

parent 1c4d4cb1
Show whitespace changes
Inline Side-by-side
Showing with 790 additions and 854 deletions
INSTALL
View file @ 5ba1fab5
PostgreSQL Installation Instructions PostgreSQL Installation Instructions
This document describes the installation of PostgreSQL from the source code This document describes the installation of PostgreSQL from the source
distribution. code distribution.
_________________________________________________________________
-------------------------------------------------------------------------------
Short Version Short Version
./configure ./configure
gmake gmake
su su
gmake install gmake install
adduser postgres adduser postgres
mkdir /usr/local/pgsql/data mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data chown postgres /usr/local/pgsql/data
su - postgres su - postgres
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 & /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 &
/usr/local/pgsql/bin/createdb test /usr/local/pgsql/bin/createdb test
/usr/local/pgsql/bin/psql test /usr/local/pgsql/bin/psql test
The long version is the rest of this document. The long version is the rest of this document.
_________________________________________________________________
-------------------------------------------------------------------------------
Requirements Requirements
In general, a modern Unix-compatible platform should be able to run PostgreSQL. In general, a modern Unix-compatible platform should be able to run
The platforms that had received specific testing at the time of release are PostgreSQL. The platforms that had received specific testing at the
listed in the Section called Supported Platforms below. In the "doc" time of release are listed in the section called Supported Platforms
subdirectory of the distribution there are several platform-specific FAQ below. In the "doc" subdirectory of the distribution there are several
documents you might wish to consult if you are having trouble. platform-specific FAQ documents you might wish to consult if you are
The following software packages are required for building PostgreSQL: having trouble.
* GNU make is required; other make programs will *not* work. GNU make is
often installed under the name "gmake"; this document will always refer
to it by that name. (On some systems GNU make is the default tool with
the name "make".) To test for GNU make enter
gmake --version The following software packages are required for building PostgreSQL:
* GNU make is required; other make programs will *not* work. GNU
make is often installed under the name "gmake"; this document will
always refer to it by that name. (On some systems GNU make is the
default tool with the name "make".) To test for GNU make enter
gmake --version
It is recommended to use version 3.76.1 or later. It is recommended to use version 3.76.1 or later.
* You need an ISO/ANSI C compiler. Recent versions of GCC are * You need an ISO/ANSI C compiler. Recent versions of GCC are
recommendable, but PostgreSQL is known to build with a wide variety of recommendable, but PostgreSQL is known to build with a wide
compilers from different vendors. variety of compilers from different vendors.
* gzip is needed to unpack the distribution in the first place. If
* gzip is needed to unpack the distribution in the first place. If you are you are reading this, you probably already got past that hurdle.
reading this, you probably already got past that hurdle.
* The GNU Readline library (for comfortable line editing and command * The GNU Readline library (for comfortable line editing and command
history retrieval) will be used by default. If you don't want to use it history retrieval) will be used by default. If you don't want to
then you must specify the "--without-readline" option for "configure". use it then you must specify the "--without-readline" option for
(On NetBSD, the "libedit" library is readline-compatible and is used if "configure". (On NetBSD, the "libedit" library is
"libreadline" is not found.) Readline-compatible and is used if "libreadline" is not found.)
* To build on Windows NT or Windows 2000 you need the Cygwin and
* To build on Windows NT or Windows 2000 you need the Cygwin and cygipc cygipc packages. See the file "doc/FAQ_MSWIN" for details.
packages. See the file "doc/FAQ_MSWIN" for details.
The following packages are optional. They are not required in the
The following packages are optional. They are not required in the default default configuration, but they are needed when certain build options
configuration, but they are needed when certain build options are enabled, as are enabled, as explained below.
explained below.
* To build the server programming language PL/Perl you need a full
* To build the server programming language PL/Perl you need a full Perl Perl installation, including the "libperl" library and the header
installation, including the "libperl" library and the header files. Since files. Since PL/Perl will be a shared library, the "libperl"
PL/Perl will be a shared library, the "libperl" library must be a shared library must be a shared library also on most platforms. This
library also on most platforms. This appears to be the default in recent appears to be the default in recent Perl versions, but it was not
Perl versions, but it was not in earlier versions, and in general it is in earlier versions, and in general it is the choice of whomever
the choice of whomever installed Perl at your site. installed Perl at your site.
If you don't have the shared library but you need one, a message like If you don't have the shared library but you need one, a message
this will appear during the build to point out this fact: like this will appear during the build to point out this fact:
*** Cannot build PL/Perl because libperl is not a shared library.
*** Cannot build PL/Perl because libperl is not a shared library. *** You might have to rebuild your Perl installation. Refer to
*** You might have to rebuild your Perl installation. Refer to *** the documentation for details.
*** the documentation for details. (If you don't follow the on-screen output you will merely notice
that the PL/Perl library object, "plperl.so" or similar, will not
(If you don't follow the on-screen output you will merely notice that the be installed.) If you see this, you will have to rebuild and
PL/Perl library object, "plperl.so" or similar, will not be installed.) install Perl manually to be able to build PL/Perl. During the
If you see this, you will have to rebuild and install Perl manually to be configuration process for Perl, request a shared library.
able to build PL/Perl. During the configuration process for Perl, request * To build the PL/Python server programming language, you need a
a shared library. Python installation, including the header files. Since PL/Python
will be a shared library, the "libpython" library must be a shared
* To build the Python interface module or the PL/Python server programming library also on most platforms. This is not the case in a default
language, you need a Python installation, including the header files. Python installation.
Since PL/Python will be a shared library, the "libpython" library must be If after building and installing you have a file called
a shared library also on most platforms. This is not the case in a "plpython.so" (possibly a different extension), then everything
default Python installation. went well. Otherwise you should have seen a notice like this
If after building and installing you have a file called "plpython.so" flying by:
(possibly a different extension), then everything went well. Otherwise *** Cannot build PL/Python because libpython is not a shared library.
you should have seen a notice like this flying by: *** You might have to rebuild your Python installation. Refer to
*** the documentation for details.
*** Cannot build PL/Python because libpython is not a shared library. That means you have to rebuild (part of) your Python installation
*** You might have to rebuild your Python installation. Refer to to supply this shared library.
*** the documentation for details. The catch is that the Python distribution or the Python
maintainers do not provide any direct way to do this. The closest
That means you have to rebuild (part of) your Python installation to thing we can offer you is the information in Python FAQ 3.30. On
supply this shared library. some operating systems you don't really have to build a shared
The catch is that the Python distribution or the Python maintainers do library, but then you will have to convince the PostgreSQL build
not provide any direct way to do this. The closest thing we can offer you system of this. Consult the "Makefile" in the "src/pl/plpython"
is the information in Python FAQ 3.30. On some operating systems you directory for details.
don't really have to build a shared library, but then you will have to
convince the PostgreSQL build system of this. Consult the "Makefile" in
the "src/pl/plpython" directory for details.
* If you want to build Tcl or Tk components (clients and the PL/Tcl * If you want to build Tcl or Tk components (clients and the PL/Tcl
language) you of course need a Tcl installation. language) you of course need a Tcl installation.
* To build the JDBC driver, you need Ant 1.5 or higher and a JDK.
* To build the JDBC driver, you need Ant 1.5 or higher and a JDK. Ant is a Ant is a special tool for building Java-based packages. It can be
special tool for building Java-based packages. It can be downloaded from downloaded from the Ant web site.
the Ant web site. If you have several Java compilers installed, it depends on the
If you have several Java compilers installed, it depends on the Ant Ant configuration which one gets used. Precompiled Ant
configuration which one gets used. Precompiled Ant distributions are distributions are typically set up to read a file ".antrc" in the
typically set up to read a file ".antrc" in the current user's home current user's home directory for configuration. For example, to
directory for configuration. For example, to use a different JDK than the use a different JDK than the default, this may work:
default, this may work: JAVA_HOME=/usr/local/sun-jdk1.3
JAVACMD=$JAVA_HOME/bin/java
JAVA_HOME=/usr/local/sun-jdk1.3
JAVACMD=$JAVA_HOME/bin/java
Note: Do not try to build the driver by calling "ant" or even Note: Do not try to build the driver by calling "ant" or even
"javac" directly. This will not work. Run "gmake" normally as "javac" directly. This will not work. Run "gmake" normally as
described below. described below.
* To enable Native Language Support (NLS), that is, the ability to
* To enable Native Language Support (NLS), that is, the ability to display display a program's messages in a language other than English, you
a program's messages in a language other than English, you need an need an implementation of the Gettext API. Some operating systems
implementation of the Gettext API. Some operating systems have this have this built-in (e.g., Linux, NetBSD, Solaris), for other
built-in (e.g., Linux, NetBSD, Solaris), for other systems you can systems you can download an add-on package from here:
download an add-on package from here: http://www.postgresql.org/~petere/ http://www.postgresql.org/~petere/gettext.html. If you are using
gettext.html. If you are using the gettext implementation in the GNU C the Gettext implementation in the GNU C library then you will
library then you will additionally need the GNU Gettext package for some additionally need the GNU Gettext package for some utility
utility programs. For any of the other implementations you will not need programs. For any of the other implementations you will not need
it. it.
* Kerberos, OpenSSL, or PAM, if you want to support authentication
* Kerberos, OpenSSL, or PAM, if you want to support authentication using using these services.
these services.
If you are building from a CVS tree instead of using a released source
If you are build from a CVS tree instead of using a released source package, or package, or if you want to do development, you also need the following
if you want to do development, you also need the following packages: packages:
* Flex and Bison are needed to build a CVS checkout or if you changed the * Flex and Bison are needed to build a CVS checkout or if you
actual scanner and parser definition files. If you need them, be sure to changed the actual scanner and parser definition files. If you
get Flex 2.5.4 or later and Bison 1.50 or later. Other yacc programs can need them, be sure to get Flex 2.5.4 or later and Bison 1.875 or
sometimes be used, but doing so requires extra effort and is not later. Other yacc programs can sometimes be used, but doing so
recommended. Other lex programs will definitely not work. requires extra effort and is not recommended. Other lex programs
will definitely not work.
If you need to get a GNU package, you can find it at your local GNU mirror site
(see http://www.gnu.org/order/ftp.html for a list) or at ftp://ftp.gnu.org/ If you need to get a GNU package, you can find it at your local GNU
gnu/. mirror site (see http://www.gnu.org/order/ftp.html for a list) or at
Also check that you have sufficient disk space. You will need about 65 MB for ftp://ftp.gnu.org/gnu/.
the source tree during compilation and about 15 MB for the installation
directory. An empty database cluster takes about 25 MB, databases take about Also check that you have sufficient disk space. You will need about 65
five times the amount of space that a flat text file with the same data would MB for the source tree during compilation and about 15 MB for the
take. If you are going to run the regression tests you will temporarily need up installation directory. An empty database cluster takes about 25 MB,
to an extra 90 MB. Use the "df" command to check for disk space. databases take about five times the amount of space that a flat text
file with the same data would take. If you are going to run the
------------------------------------------------------------------------------- regression tests you will temporarily need up to an extra 90 MB. Use
the "df" command to check for disk space.
_________________________________________________________________
If You Are Upgrading If You Are Upgrading
The internal data storage format changes with new releases of PostgreSQL. The internal data storage format changes with new releases of
Therefore, if you are upgrading an existing installation that does not have a PostgreSQL. Therefore, if you are upgrading an existing installation
version number "7.3.x", you must back up and restore your data as shown here. that does not have a version number "7.4.x", you must back up and
These instructions assume that your existing installation is under the "/usr/ restore your data as shown here. These instructions assume that your
local/pgsql" directory, and that the data area is in "/usr/local/pgsql/data". existing installation is under the "/usr/local/pgsql" directory, and
Substitute your paths appropriately. that the data area is in "/usr/local/pgsql/data". Substitute your
paths appropriately.
1. Make sure that your database is not updated during or after the backup. 1. Make sure that your database is not updated during or after the
This does not affect the integrity of the backup, but the changed data backup. This does not affect the integrity of the backup, but the
would of course not be included. If necessary, edit the permissions in changed data would of course not be included. If necessary, edit
the file "/usr/local/pgsql/data/pg_hba.conf" (or equivalent) to disallow the permissions in the file "/usr/local/pgsql/data/pg_hba.conf"
access from everyone except you. (or equivalent) to disallow access from everyone except you.
2. To back up your database installation, type: 2. To back up your database installation, type:
pg_dumpall > outputfile
pg_dumpall > outputfile If you need to preserve OIDs (such as when using them as foreign
keys), then use the "-o" option when running "pg_dumpall".
If you need to preserve OIDs (such as when using them as foreign keys), "pg_dumpall" does not save large objects. Check the documentation
then use the "-o" option when running "pg_dumpall".
"pg_dumpall" does not save large objects. Check the Administrator's Guide
if you need to do this. if you need to do this.
To make the backup, you can use the "pg_dumpall" command from the version To make the backup, you can use the "pg_dumpall" command from the
you are currently running. For best results, however, try to use the version you are currently running. For best results, however, try
"pg_dumpall" command from PostgreSQL 7.3, since this version contains to use the "pg_dumpall" command from PostgreSQL 7.4beta4, since
bug fixes and improvements over older versions. While this advice might this version contains bug fixes and improvements over older
seem idiosyncratic since you haven't installed the new version yet, it is versions. While this advice might seem idiosyncratic since you
advisable to follow it if you plan to install the new version in parallel haven't installed the new version yet, it is advisable to follow
with the old version. In that case you can complete the installation it if you plan to install the new version in parallel with the old
normally and transfer the data later. This will also decrease the version. In that case you can complete the installation normally
downtime. and transfer the data later. This will also decrease the downtime.
3. If you are installing the new version at the same location as the
3. If you are installing the new version at the same location as the old one old one then shut down the old server, at the latest before you
then shut down the old server, at the latest before you install the new install the new files:
files: kill -INT `cat /usr/local/pgsql/data/postmaster.pid`
Versions prior to 7.0 do not have this "postmaster.pid" file. If
kill -INT `cat /usr/local/pgsql/data/postmaster.pid` you are using such a version you must find out the process ID of
the server yourself, for example by typing "ps ax | grep
Versions prior to 7.0 do not have this "postmaster.pid" file. If you are postmaster", and supply it to the "kill" command.
using such a version you must find out the process id of the server On systems that have PostgreSQL started at boot time, there is
yourself, for example by typing "ps ax | grep postmaster", and supply it probably a start-up file that will accomplish the same thing. For
to the "kill" command. example, on a Red Hat Linux system one might find that
On systems that have PostgreSQL started at boot time, there is probably a /etc/rc.d/init.d/postgresql stop
start-up file that will accomplish the same thing. For example, on a Red
Hat Linux system one might find that
/etc/rc.d/init.d/postgresql stop
works. Another possibility is "pg_ctl stop". works. Another possibility is "pg_ctl stop".
4. If you are installing in the same place as the old version then it
is also a good idea to move the old installation out of the way,
in case you have trouble and need to revert to it. Use a command
like this:
mv /usr/local/pgsql /usr/local/pgsql.old
4. If you are installing in the same place as the old version then it is After you have installed PostgreSQL 7.4beta4, create a new database
also a good idea to move the old installation out of the way, in case you directory and start the new server. Remember that you must execute
have trouble and need to revert to it. Use a command like this: these commands while logged in to the special database user account
(which you already have if you are upgrading).
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
mv /usr/local/pgsql /usr/local/pgsql.old Finally, restore your data with
/usr/local/pgsql/bin/psql -d template1 -f outputfile
After you have installed PostgreSQL 7.3, create a new database directory and using the *new* psql.
start the new server. Remember that you must execute these commands while
logged in to the special database user account (which you already have if you
are upgrading).
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data These topics are discussed at length in the documentation, which you
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data are encouraged to read in any case.
_________________________________________________________________
Finally, restore your data with
/usr/local/pgsql/bin/psql -d template1 -f outputfile
using the *new* psql.
These topics are discussed at length in the Administrator's Guide, which you
are encouraged to read in any case.
-------------------------------------------------------------------------------
Installation Procedure Installation Procedure
1. Configuration 1. Configuration
The first step of the installation procedure is to configure the source The first step of the installation procedure is to configure the
tree for your system and choose the options you would like. This is done source tree for your system and choose the options you would like.
by running the "configure" script. For a default installation simply This is done by running the "configure" script. For a default
enter installation simply enter
./configure
./configure This script will run a number of tests to guess values for various
system dependent variables and detect some quirks of your
This script will run a number of tests to guess values for various system operating system, and finally will create several files in the
dependent variables and detect some quirks of your operating system, and build tree to record what it found. (You can also run "configure"
finally will create several files in the build tree to record what it in a directory outside the source tree if you want to keep the
found. (You can also run "configure" in a directory outside the source build directory separate.)
tree if you want to keep the build directory separate.) The default configuration will build the server and utilities, as
The default configuration will build the server and utilities, as well as well as all client applications and interfaces that require only a
all client applications and interfaces that require only a C compiler. C compiler. All files will be installed under "/usr/local/pgsql"
All files will be installed under "/usr/local/pgsql" by default. by default.
You can customize the build and installation process by supplying one or You can customize the build and installation process by supplying
more of the following command line options to "configure": one or more of the following command line options to "configure":
--prefix=PREFIX --prefix=PREFIX
Install all files under the directory "PREFIX" instead of
"/usr/local/pgsql". The actual files will be installed
into various subdirectories; no files will ever be
installed directly into the "PREFIX" directory.
Install all files under the directory "PREFIX" instead of "/usr/ If you have special needs, you can also customize the
local/pgsql". The actual files will be installed into various individual subdirectories with the following options.
subdirectories; no files will ever be installed directly into the
"PREFIX" directory.
If you have special needs, you can also customize the individual
subdirectories with the following options.
--exec-prefix=EXEC-PREFIX --exec-prefix=EXEC-PREFIX
You can install architecture-dependent files under a
You can install architecture-dependent files under a different different prefix, "EXEC-PREFIX", than what "PREFIX" was
prefix, "EXEC-PREFIX", than what "PREFIX" was set to. This can be set to. This can be useful to share
useful to share architecture-independent files between hosts. If architecture-independent files between hosts. If you omit
you omit this, then "EXEC-PREFIX" is set equal to "PREFIX" and both this, then "EXEC-PREFIX" is set equal to "PREFIX" and
architecture-dependent and independent files will be installed both architecture-dependent and independent files will be
under the same tree, which is probably what you want. installed under the same tree, which is probably what you
want.
--bindir=DIRECTORY --bindir=DIRECTORY
Specifies the directory for executable programs. The
Specifies the directory for executable programs. The default is default is "EXEC-PREFIX/bin", which normally means
"EXEC-PREFIX/bin", which normally means "/usr/local/pgsql/bin". "/usr/local/pgsql/bin".
--datadir=DIRECTORY --datadir=DIRECTORY
Sets the directory for read-only data files used by the
Sets the directory for read-only data files used by the installed installed programs. The default is "PREFIX/share". Note
programs. The default is "PREFIX/share". Note that this has nothing that this has nothing to do with where your database
to do with where your database files will be placed. files will be placed.
--sysconfdir=DIRECTORY --sysconfdir=DIRECTORY
The directory for various configuration files,
The directory for various configuration files, "PREFIX/etc" by "PREFIX/etc" by default.
default.
--libdir=DIRECTORY --libdir=DIRECTORY
The location to install libraries and dynamically
The location to install libraries and dynamically loadable modules. loadable modules. The default is "EXEC-PREFIX/lib".
The default is "EXEC-PREFIX/lib".
--includedir=DIRECTORY --includedir=DIRECTORY
The directory for installing C and C++ header files. The
The directory for installing C and C++ header files. The default is default is "PREFIX/include".
"PREFIX/include".
--docdir=DIRECTORY --docdir=DIRECTORY
Documentation files, except "man" pages, will be
Documentation files, except "man" pages, will be installed into installed into this directory. The default is
this directory. The default is "PREFIX/doc". "PREFIX/doc".
--mandir=DIRECTORY --mandir=DIRECTORY
The man pages that come with PostgreSQL will be installed
The man pages that come with PostgreSQL will be installed under under this directory, in their respective "manx"
this directory, in their respective "manx" subdirectories. The subdirectories. The default is "PREFIX/man".
default is "PREFIX/man".
Note: Care has been taken to make it possible to install Note: Care has been taken to make it possible to install PostgreSQL
PostgreSQL into shared installation locations (such as "/usr/ into shared installation locations (such as "/usr/local/include")
local/include") without interfering with the namespace of the without interfering with the namespace of the rest of the system.
rest of the system. First, the string "/postgresql" is First, the string "/postgresql" is automatically appended to
automatically appended to datadir, sysconfdir, and docdir, datadir, sysconfdir, and docdir, unless the fully expanded
unless the fully expanded directory name already contains the directory name already contains the string "postgres" or "pgsql".
string "postgres" or "pgsql". For example, if you choose "/usr/ For example, if you choose "/usr/local" as prefix, the
local" as prefix, the documentation will be installed in "/usr/ documentation will be installed in "/usr/local/doc/postgresql", but
local/doc/postgresql", but if the prefix is "/opt/postgres", if the prefix is "/opt/postgres", then it will be in
then it will be in "/opt/postgres/doc". The public C header "/opt/postgres/doc". The public C header files of the client
files of the client interfaces are installed into includedir interfaces are installed into includedir and are namespace-clean.
and are namespace-clean. The internal header files and the The internal header files and the server header files are installed
server header files are installed into private directories into private directories under includedir. See the documentation of
under includedir. See the Programmer's Guide for information each interface for information about how to get at the its header
about how to get at the header files for each interface. files. Finally, a private subdirectory will also be created, if
Finally, a private subdirectory will also be created, if
appropriate, under libdir for dynamically loadable modules. appropriate, under libdir for dynamically loadable modules.
--with-includes=DIRECTORIES --with-includes=DIRECTORIES
"DIRECTORIES" is a colon-separated list of directories
that will be added to the list the compiler searches for
header files. If you have optional packages (such as GNU
Readline) installed in a non-standard location, you have
to use this option and probably also the corresponding
"--with-libraries" option.
"DIRECTORIES" is a colon-separated list of directories that will be Example:
added to the list the compiler searches for header files. If you --with-includes=/opt/gnu/include:/usr/sup/include.
have optional packages (such as GNU Readline) installed in a non-
standard location, you have to use this option and probably also
the corresponding "--with-libraries" option.
Example: --with-includes=/opt/gnu/include:/usr/sup/include.
--with-libraries=DIRECTORIES --with-libraries=DIRECTORIES
"DIRECTORIES" is a colon-separated list of directories to
search for libraries. You will probably have to use this
option (and the corresponding "--with-includes" option)
if you have packages installed in non-standard locations.
"DIRECTORIES" is a colon-separated list of directories to search
for libraries. You will probably have to use this option (and the
corresponding "--with-includes" option) if you have packages
installed in non-standard locations.
Example: --with-libraries=/opt/gnu/lib:/usr/sup/lib. Example: --with-libraries=/opt/gnu/lib:/usr/sup/lib.
--enable-nls[=LANGUAGES] --enable-nls[=LANGUAGES]
Enables Native Language Support (NLS), that is, the
Enables Native Language Support (NLS), that is, the ability to ability to display a program's messages in a language
display a program's messages in a language other than English. other than English. "LANGUAGES" is a space separated list
"LANGUAGES" is a space separated list of codes of the languages of codes of the languages that you want supported, for
that you want supported, for example --enable-nls='de fr'. (The example --enable-nls='de fr'. (The intersection between
intersection between your list and the set of actually provided your list and the set of actually provided translations
translations will be computed automatically.) If you do not specify will be computed automatically.) If you do not specify a
a list, then all available translations are installed. list, then all available translations are installed.
To use this option, you will need an implementation of the gettext
API; see above. To use this option, you will need an implementation of
the Gettext API; see above.
--with-pgport=NUMBER --with-pgport=NUMBER
Set "NUMBER" as the default port number for server and
Set "NUMBER" as the default port number for server and clients. The clients. The default is 5432. The port can always be
default is 5432. The port can always be changed later on, but if changed later on, but if you specify it here then both
you specify it here then both server and clients will have the same server and clients will have the same default compiled
default compiled in, which can be very convenient. Usually the only in, which can be very convenient. Usually the only good
good reason to select a non-default value is if you intend to run reason to select a non-default value is if you intend to
multiple PostgreSQL servers on the same machine. run multiple PostgreSQL servers on the same machine.
--with-perl --with-perl
Build the PL/Perl server-side language. Build the PL/Perl server-side language.
--with-python --with-python
Build the PL/Python server-side language.
Build the Python interface module and the PL/Python server-side
language. You need to have root access to be able to install the
Python module at its default place ("/usr/lib/pythonx.y").
--with-tcl --with-tcl
Build components that require Tcl/Tk, which are libpgtcl,
Build components that require Tcl/Tk, which are libpgtcl, pgtclsh, pgtclsh, pgtksh, and PL/Tcl. But see below about
pgtksh, and PL/Tcl. But see below about "--without-tk". "--without-tk".
--without-tk --without-tk
If you specify "--with-tcl" and this option, then the
If you specify "--with-tcl" and this option, then the program that program that requires Tk (pgtksh) will be excluded.
requires Tk (pgtksh) will be excluded.
--with-tclconfig=DIRECTORY, --with-tkconfig=DIRECTORY --with-tclconfig=DIRECTORY, --with-tkconfig=DIRECTORY
Tcl/Tk installs the files "tclConfig.sh" and
Tcl/Tk installs the files "tclConfig.sh" and "tkConfig.sh", which "tkConfig.sh", which contain configuration information
contain configuration information needed to build modules needed to build modules interfacing to Tcl or Tk. These
interfacing to Tcl or Tk. These files are normally found files are normally found automatically at their
automatically at their well-known locations, but if you want to use well-known locations, but if you want to use a different
a different version of Tcl or Tk you can specify the directory in version of Tcl or Tk you can specify the directory in
which to find them. which to find them.
--with-java --with-java
Build the JDBC driver and associated Java packages. Build the JDBC driver and associated Java packages.
--with-krb4[=DIRECTORY], --with-krb5[=DIRECTORY] --with-krb4[=DIRECTORY], --with-krb5[=DIRECTORY]
Build with support for Kerberos authentication. You can
Build with support for Kerberos authentication. You can use either use either Kerberos version 4 or 5, but not both. The
Kerberos version 4 or 5, but not both. The "DIRECTORY" argument "DIRECTORY" argument specifies the root directory of the
specifies the root directory of the Kerberos installation; "/usr/ Kerberos installation; "/usr/athena" is assumed as
athena" is assumed as default. If the relevant header files and default. If the relevant header files and libraries are
libraries are not under a common parent directory, then you must not under a common parent directory, then you must use
use the "--with-includes" and "--with-libraries" options in the "--with-includes" and "--with-libraries" options in
addition to this option. If, on the other hand, the required files addition to this option. If, on the other hand, the
are in a location that is searched by default (e.g., "/usr/lib"), required files are in a location that is searched by
then you can leave off the argument. default (e.g., "/usr/lib"), then you can leave off the
"configure" will check for the required header files and libraries argument.
to make sure that your Kerberos installation is sufficient before
proceeding. "configure" will check for the required header files and
libraries to make sure that your Kerberos installation is
sufficient before proceeding.
--with-krb-srvnam=NAME --with-krb-srvnam=NAME
The name of the Kerberos service principal. postgres is
The name of the Kerberos service principal. postgres is the the default. There's probably no reason to change this.
default. There's probably no reason to change this.
--with-openssl[=DIRECTORY] --with-openssl[=DIRECTORY]
Build with support for SSL (encrypted) connections. This
requires the OpenSSL package to be installed. The
"DIRECTORY" argument specifies the root directory of the
OpenSSL installation; the default is "/usr/local/ssl".
Build with support for SSL (encrypted) connections. This requires "configure" will check for the required header files and
the OpenSSL package to be installed. The "DIRECTORY" argument libraries to make sure that your OpenSSL installation is
specifies the root directory of the OpenSSL installation; the sufficient before proceeding.
default is "/usr/local/ssl".
"configure" will check for the required header files and libraries
to make sure that your OpenSSL installation is sufficient before
proceeding.
--with-pam --with-pam
Build with PAM (Pluggable Authentication Modules)
Build with PAM (Pluggable Authentication Modules) support. support.
--without-readline --without-readline
Prevents the use of the Readline library. This disables
command-line editing and history in psql, so it is not
recommended.
Prevents the use of the Readline library. This disables command- --with-rendezvous
line editing and history in psql, so it is not recommended. Build with Rendezvous support.
--without-zlib --disable-spinlocks
Allows source builds to succeed without CPU spinlock
support. Lack of spinlock support will produce poor
performance. This option is to be used only by platforms
lacking spinlock support.
Prevents the use of the Zlib library. This disables compression --enable-thread-safety
support in pg_dump. This option is only intended for those rare Allow separate libpq and ecpg threads to safely control
systems where this library is not available. their private connection handles.
--enable-debug --without-zlib
Prevents the use of the Zlib library. This disables
compression support in pg_dump. This option is only
intended for those rare systems where this library is not
available.
Compiles all programs and libraries with debugging symbols. This --enable-debug
means that you can run the programs through a debugger to analyze Compiles all programs and libraries with debugging
problems. This enlarges the size of the installed executables symbols. This means that you can run the programs through
considerably, and on non-GCC compilers it usually also disables a debugger to analyze problems. This enlarges the size of
compiler optimization, causing slowdowns. However, having the the installed executables considerably, and on non-GCC
symbols available is extremely helpful for dealing with any compilers it usually also disables compiler optimization,
problems that may arise. Currently, this option is recommended for causing slowdowns. However, having the symbols available
production installations only if you use GCC. But you should always is extremely helpful for dealing with any problems that
have it on if you are doing development work or running a beta may arise. Currently, this option is recommended for
version. 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.
--enable-cassert --enable-cassert
Enables assertion checks in the server, which test for
Enables assertion checks in the server, which test for many "can't many "can't happen" conditions. This is invaluable for
happen" conditions. This is invaluable for code development code development purposes, but the tests slow things down
purposes, but the tests slow things down a little. Also, having the a little. Also, having the tests turned on won't
tests turned on won't necessarily enhance the stability of your necessarily enhance the stability of your server! The
server! The assertion checks are not categorized for severity, and assertion checks are not categorized for severity, and so
so what might be a relatively harmless bug will still lead to what might be a relatively harmless bug will still lead
server restarts if it triggers an assertion failure. Currently, to server restarts if it triggers an assertion failure.
this option is not recommended for production use, but you should Currently, this option is not recommended for production
have it on for development work or when running a beta version. use, but you should have it on for development work or
when running a beta version.
--enable-depend --enable-depend
Enables automatic dependency tracking. With this option,
Enables automatic dependency tracking. With this option, the the makefiles are set up so that all affected object
makefiles are set up so that all affected object files will be files will be rebuilt when any header file is changed.
rebuilt when any header file is changed. This is useful if you are This is useful if you are doing development work, but is
doing development work, but is just wasted overhead if you intend just wasted overhead if you intend only to compile once
only to compile once and install. At present, this option will work and install. At present, this option will work only if
only if you use GCC. you use GCC.
If you prefer a C compiler different from the one "configure" picks then If you prefer a C compiler different from the one "configure"
you can set the environment variable CC to the program of your choice. By picks then you can set the environment variable CC to the program
default, "configure" will pick "gcc" unless this is inappropriate for the of your choice. By default, "configure" will pick "gcc" unless
platform. Similarly, you can override the default compiler flags with the this is inappropriate for the platform. Similarly, you can
CFLAGS variable. override the default compiler flags with the CFLAGS variable.
You can specify environment variables on the "configure" command
You can specify environment variables on the "configure" command line, line, for example:
for example: ./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'
./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'
2. Build 2. Build
To start the build, type To start the build, type
gmake
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
(Remember to use GNU make.) The build may take anywhere from 5 minutes to displayed should be
half an hour depending on your hardware. The last line displayed should All of PostgreSQL is successfully made. Ready to install.
be
All of PostgreSQL is successfully made. Ready to install.
3. Regression Tests 3. Regression Tests
If you want to test the newly built server before you install it, you can If you want to test the newly built server before you install it,
run the regression tests at this point. The regression tests are a test you can run the regression tests at this point. The regression
suite to verify that PostgreSQL runs on your machine in the way the tests are a test suite to verify that PostgreSQL runs on your
developers expected it to. Type machine in the way the developers expected it to. Type
gmake check
gmake check (This won't work as root; do it as an unprivileged user.) It is
possible that some tests fail, due to differences in error message
(This won't work as root; do it as an unprivileged user.) It is possible wording or floating point results. The file
that some tests fail, due to differences in error message wording or "src/test/regress/README" and the documentation contain detailed
floating point results. The file "src/test/regress/README" and the information about interpreting the test results. You can repeat
Administrator's Guide contain detailed information about interpreting the this test at any later time by issuing the same command.
test results. You can repeat this test at any later time by issuing the
same command.
4. Installing The Files 4. Installing The Files
Note: If you are upgrading an existing system and are going to Note: If you are upgrading an existing system and are going to
install the new files over the old ones, then you should have 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 backed up your data and shut down the old server by now, as
explained in the Section called If You Are Upgrading above. explained in the section called If You Are Upgrading above.
To install PostgreSQL enter To install PostgreSQL enter
gmake install
gmake install This will install files into the directories that were specified
in step 1. Make sure that you have appropriate permissions to
This will install files into the directories that were specified in step write into that area. Normally you need to do this step as root.
1. Make sure that you have appropriate permissions to write into that Alternatively, you could create the target directories in advance
area. Normally you need to do this step as root. Alternatively, you could and arrange for appropriate permissions to be granted.
create the target directories in advance and arrange for appropriate You can use gmake install-strip instead of gmake install to strip
permissions to be granted. the executable files and libraries as they are installed. This
You can use gmake install-strip instead of gmake install to strip the will save some space. If you built with debugging support,
executable files and libraries as they are installed. This will save some stripping will effectively remove the debugging support, so it
space. If you built with debugging support, stripping will effectively should only be done if debugging is no longer needed.
remove the debugging support, so it should only be done if debugging is install-strip tries to do a reasonable job saving space, but it
no longer needed. install-strip tries to do a reasonable job saving does not have perfect knowledge of how to strip every unneeded
space, but it does not have perfect knowledge of how to strip every byte from an executable file, so if you want to save all the disk
unneeded byte from an executable file, so if you want to save all the space you possibly can, you will have to do manual work.
disk space you possibly can, you will have to do manual work. The standard installation provides only the header files needed
If you built the Python interfaces and you were not the root user when for client application development. If you plan to do any
you executed the above command then that part of the installation server-side program development (such as custom functions or data
probably failed. In that case you should become the root user and then do types written in C), then you may want to install the entire
PostgreSQL include tree into your target include directory. To do
gmake -C src/interfaces/python install that, enter
gmake install-all-headers
If you do not have superuser access you are on your own: you can still This adds a megabyte or two to the installation footprint, and is
take the required files and place them in other directories where Python only useful if you don't plan to keep the whole source tree around
can find them, but how to do that is left as an exercise. for reference. (If you do, you can just use the source's include
The standard installation provides only the header files needed for directory when building server-side software.)
client application development. If you plan to do any server-side program
development (such as custom functions or data types written in C), then
you may want to install the entire PostgreSQL include tree into your
target include directory. To do that, enter
gmake install-all-headers
This adds a megabyte or two to the installation footprint, and is only
useful if you don't plan to keep the whole source tree around for
reference. (If you do, you can just use the source's include directory
when building server-side software.)
Client-only installation: If you want to install only the client Client-only installation: If you want to install only the client
applications and interface libraries, then you can use these commands: applications and interface libraries, then you can use these
commands:
gmake -C src/bin install gmake -C src/bin install
gmake -C src/include install gmake -C src/include install
gmake -C src/interfaces install gmake -C src/interfaces install
gmake -C doc install gmake -C doc install
Uninstallation: To undo the installation use the command "gmake uninstall". Uninstallation: To undo the installation use the command "gmake
However, this will not remove any created directories. 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 Cleaning: After the installation you can make room by removing the
files made by the configure program, so that you can rebuild everything with built files from the source tree with the command "gmake clean". This
"gmake" later on. To reset the source tree to the state in which it was will preserve the files made by the "configure" program, so that you
distributed, use "gmake distclean". If you are going to build for several can rebuild everything with "gmake" later on. To reset the source tree
platforms from the same source tree you must do this and re-configure for each to the state in which it was distributed, use "gmake distclean". If
build. you are going to build for several platforms from the same source tree
If you perform a build and then discover that your configure options were you must do this and re-configure for each build.
wrong, or if you change anything that configure investigates (for example,
software upgrades), then it's a good idea to do "gmake distclean" before If you perform a build and then discover that your "configure" options
reconfiguring and rebuilding. Without this, your changes in configuration were wrong, or if you change anything that "configure" investigates
choices may not propagate everywhere they need to. (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 Post-Installation Setup
Shared Libraries Tuning
On some systems that have shared libraries (which most systems do) you need to By default, PostgreSQL is configured to run on minimal hardware. This
tell your system how to find the newly installed shared libraries. The systems allows it to start up with almost any hardware configuration. However,
on which this is *not* necessary include BSD/OS, FreeBSD, HP-UX, IRIX, Linux, the default configuration is not designed for optimum performance. To
NetBSD, OpenBSD, Tru64 UNIX (formerly Digital UNIX), and Solaris. achieve optimum performance, several server variables must be
The method to set the shared library search path varies between platforms, but adjusted, the two most common being shared_buffers and sort_mem
the most widely usable method is to set the environment variable mentioned in the documentation . Other parameters in the documentation
LD_LIBRARY_PATH like so: In Bourne shells ("sh", "ksh", "bash", "zsh") also affect performance.
_________________________________________________________________
LD_LIBRARY_PATH=/usr/local/pgsql/lib
export LD_LIBRARY_PATH Shared Libraries
or in "csh" or "tcsh" On some systems that have shared libraries (which most systems do) you
need to tell your system how to find the newly installed shared
setenv LD_LIBRARY_PATH /usr/local/pgsql/lib libraries. The systems on which this is *not* necessary include
BSD/OS, FreeBSD, HP-UX, IRIX, Linux, NetBSD, OpenBSD, Tru64 UNIX
Replace /usr/local/pgsql/lib with whatever you set "--libdir" to in step 1. You (formerly Digital UNIX), and Solaris.
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 The method to set the shared library search path varies between
method can be found at http://www.visi.com/~barr/ldpath.html. platforms, but the most widely usable method is to set the environment
On some systems it might be preferable to set the environment variable variable LD_LIBRARY_PATH like so: In Bourne shells ("sh", "ksh",
LD_RUN_PATH *before* building. "bash", "zsh")
On Cygwin, put the library directory in the PATH or move the ".dll" files into LD_LIBRARY_PATH=/usr/local/pgsql/lib
the "bin/" directory. export LD_LIBRARY_PATH
If in doubt, refer to the manual pages of your system (perhaps "ld.so" or
"rld"). If you later on get a message like or in "csh" or "tcsh"
setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
psql: error in loading shared libraries
libpq.so.2.1: cannot open shared object file: No such file or directory Replace /usr/local/pgsql/lib with whatever you set "--libdir" to in
step 1. You should put these commands into a shell start-up file such
then this step was necessary. Simply take care of it then. as "/etc/profile" or "~/.bash_profile". Some good information about
If you are on BSD/OS, Linux, or SunOS 4 and you have root access you can run the caveats associated with this method can be found at
http://www.visi.com/~barr/ldpath.html.
/sbin/ldconfig /usr/local/pgsql/lib
On some systems it might be preferable to set the environment variable
(or equivalent directory) after installation to enable the run-time linker to LD_RUN_PATH *before* building.
find the shared libraries faster. Refer to the manual page of "ldconfig" for
more information. On FreeBSD, NetBSD, and OpenBSD the command is On Cygwin, put the library directory in the PATH or move the ".dll"
files into the "bin" directory.
/sbin/ldconfig -m /usr/local/pgsql/lib
If in doubt, refer to the manual pages of your system (perhaps "ld.so"
instead. Other systems are not known to have an equivalent command. 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
Environment Variables then this step was necessary. Simply take care of it then.
If you installed into "/usr/local/pgsql" or some other location that is not If you are on BSD/OS, Linux, or SunOS 4 and you have root access you
searched for programs by default, you should add "/usr/local/pgsql/bin" (or can run
whatever you set "--bindir" to in step 1) into your PATH. Strictly speaking, /sbin/ldconfig /usr/local/pgsql/lib
this is not necessary, but it will make the use of PostgreSQL much more
convenient. (or equivalent directory) after installation to enable the run-time
To do this, add the following to your shell start-up file, such as linker to find the shared libraries faster. Refer to the manual page
"~/.bash_profile" (or "/etc/profile", if you want it to affect every user): of "ldconfig" for more information. On FreeBSD, NetBSD, and OpenBSD
the command is
PATH=/usr/local/pgsql/bin:$PATH /sbin/ldconfig -m /usr/local/pgsql/lib
export PATH
instead. Other systems are not known to have an equivalent command.
If you are using "csh" or "tcsh", then use this command: _________________________________________________________________
set path = ( /usr/local/pgsql/bin $path ) Environment Variables
To enable your system to find the man documentation, you need to add a line If you installed into "/usr/local/pgsql" or some other location that
like the following to a shell start-up file unless you installed into a is not searched for programs by default, you should add
location that is searched by default. "/usr/local/pgsql/bin" (or whatever you set "--bindir" to in step 1)
into your PATH. Strictly speaking, this is not necessary, but it will
MANPATH=/usr/local/pgsql/man:$MANPATH make the use of PostgreSQL much more convenient.
export MANPATH
To do this, add the following to your shell start-up file, such as
The environment variables PGHOST and PGPORT specify to client applications the "~/.bash_profile" (or "/etc/profile", if you want it to affect every
host and port of the database server, overriding the compiled-in defaults. If user):
you are going to run client applications remotely then it is convenient if PATH=/usr/local/pgsql/bin:$PATH
every user that plans to use the database sets PGHOST. This is not required, export PATH
however: the settings can be communicated via command line options to most
client programs. If you are using "csh" or "tcsh", then use this command:
set path = ( /usr/local/pgsql/bin $path )
-------------------------------------------------------------------------------
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 Getting Started
The following is a quick summary of how to get PostgreSQL up and running once The following is a quick summary of how to get PostgreSQL up and
installed. The Administrator's Guide contains more information. running once installed. The main documentation contains more
information.
1. Create a user account for the PostgreSQL server. This is the user the 1. Create a user account for the PostgreSQL server. This is the user
server will run as. For production use you should create a separate, the server will run as. For production use you should create a
unprivileged account ("postgres" is commonly used). If you do not have separate, unprivileged account ("postgres" is commonly used). If
root access or just want to play around, your own user account is enough, you do not have root access or just want to play around, your own
but running the server as root is a security risk and will not work. user account is enough, but running the server as root is a
security risk and will not work.
adduser postgres adduser postgres
2. Create a database installation with the "initdb" command. To run
2. Create a database installation with the "initdb" command. To run "initdb" "initdb" you must be logged in to your PostgreSQL server account.
you must be logged in to your PostgreSQL server account. It will not work It will not work as root.
as root. root# mkdir /usr/local/pgsql/data
root# chown postgres /usr/local/pgsql/data
root# mkdir /usr/local/pgsql/data root# su - postgres
root# chown postgres /usr/local/pgsql/data postgres$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
root# su - postgres The "-D" option specifies the location where the data will be
postgres$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data stored. You can use any path you want, it does not have to be
under the installation directory. Just make sure that the server
The "-D" option specifies the location where the data will be stored. You account can write to the directory (or create it, if it doesn't
can use any path you want, it does not have to be under the installation already exist) before starting "initdb", as illustrated here.
directory. Just make sure that the server account can write to the 3. The previous step should have told you how to start up the
directory (or create it, if it doesn't already exist) before starting database server. Do so now. The command should look something like
"initdb", as illustrated here. /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
This will start the server in the foreground. To put the server in
3. The previous step should have told you how to start up the database the background use something like
server. Do so now. The command should look something like nohup /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data \
/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
This will start the server in the foreground. To put the server in the
background use something like
nohup /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data \
</dev/null >>server.log 2>&1 </dev/null & </dev/null >>server.log 2>&1 </dev/null &
To stop a server running in the background you can type To stop a server running in the background you can type
kill `cat /usr/local/pgsql/data/postmaster.pid`
kill `cat /usr/local/pgsql/data/postmaster.pid` In order to allow TCP/IP connections (rather than only Unix domain
socket ones) you need to pass the "-i" option to "postmaster".
In order to allow TCP/IP connections (rather than only Unix domain socket
ones) you need to pass the "-i" option to "postmaster".
4. Create a database: 4. Create a database:
createdb testdb
createdb testdb
Then enter Then enter
psql testdb
psql testdb to connect to that database. At the prompt you can enter SQL
commands and start experimenting.
to connect to that database. At the prompt you can enter SQL commands and _________________________________________________________________
start experimenting.
-------------------------------------------------------------------------------
What Now? What Now?
* The PostgreSQL distribution contains a comprehensive documentation set, * The PostgreSQL distribution contains a comprehensive documentation
which you should read sometime. After installation, the documentation can set, which you should read sometime. After installation, the
be accessed by pointing your browser to "/usr/local/pgsql/doc/html/ documentation can be accessed by pointing your browser to
index.html", unless you changed the installation directories. "/usr/local/pgsql/doc/html/index.html", unless you changed the
The Tutorial should be your first reading if you are completely new to installation directories.
SQL databases. If you are familiar with database concepts then you want The first few chapters of the main documentation are the Tutorial,
to proceed with the Administrator's Guide, which contains information which should be your first reading if you are completely new to
about how to set up the database server, database users, and SQL databases. If you are familiar with database concepts then you
authentication. want to proceed with part on server administration, which contains
information about how to set up the database server, database
users, and authentication.
* Usually, you will want to modify your computer so that it will * Usually, you will want to modify your computer so that it will
automatically start the database server whenever it boots. Some automatically start the database server whenever it boots. Some
suggestions for this are in the Administrator's Guide. suggestions for this are in the documentation.
* Run the regression tests against the installed server (using the * Run the regression tests against the installed server (using the
sequential test method). If you didn't run the tests before installation, sequential test method). If you didn't run the tests before
you should definitely do it now. This is also explained in the installation, you should definitely do it now. This is also
Administrator's Guide. explained in the documentation.
_________________________________________________________________
-------------------------------------------------------------------------------
Supported Platforms Supported Platforms
PostgreSQL has been verified by the developer community to work on the PostgreSQL has been verified by the developer community to work on the
platforms listed below. A supported platform generally means that PostgreSQL platforms listed below. A supported platform generally means that
builds and installs according to these instructions and that the regression PostgreSQL builds and installs according to these instructions and
tests pass. that the regression tests pass.
Note: If you are having problems with the installation on a supported
platform, please write to <pgsql-bugs@postgresql.org> or <pgsql- Note: If you are having problems with the installation on a
ports@postgresql.org>, not to the people listed here. supported platform, please write to <pgsql-bugs@postgresql.org> or
________________________________________________________________________________ <pgsql-ports@postgresql.org>, not to the people listed here.
|OS______|Processor__|Version|Reported_________________________|Remarks__________|
|AIX |RS6000 |7.3 |2002-11-12, Andreas Zeugswetter |see also doc/ | OS Processor Version Reported Remarks
|________|___________|_______|(<ZeugswetterA@spardat.at>)______|FAQ_AIX__________| AIX RS6000 7.3 2002-11-12, Andreas Zeugswetter
|BSD/OS |x86 |7.3 |2002-10-25, Bruce Momjian |4.2 | (<ZeugswetterA@spardat.at>) see also doc/FAQ_AIX
|________|___________|_______|(<pgman@candle.pha.pa.us>)_______|_________________| BSD/OS x86 7.3 2002-10-25, Bruce Momjian (<pgman@candle.pha.pa.us>)
|FreeBSD |Alpha |7.3 |2002-11-13, Chris Kings-Lynne | | 4.2
|________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________| FreeBSD Alpha 7.3 2002-11-13, Chris Kings-Lynne
|FreeBSD |x86 |7.3 |2002-10-29, 3.3, Nigel J. Andrews| | (<chriskl@familyhealth.com.au>)
| | | |(<nandrews@investsystems.co.uk>),| | FreeBSD x86 7.3 2002-10-29, 3.3, Nigel J. Andrews
| | | |4.7, Larry Rosenman | | (<nandrews@investsystems.co.uk>), 4.7, Larry Rosenman
| | | |(<ler@lerctr.org>), 5.0, Sean | | (<ler@lerctr.org>), 5.0, Sean Chittenden (<sean@chittenden.org>)
| | | |Chittenden | | HP-UX PA-RISC 7.3 2002-10-28, 10.20 Tom Lane (<tgl@sss.pgh.pa.us>),
|________|___________|_______|(<sean@chittenden.org>)__________|_________________| 11.00, 11.11, 32 and 64 bit, Giles Lean (<giles@nemeton.com.au>) gcc
|HP-UX |PA-RISC |7.3 |2002-10-28, 10.20 Tom Lane |gcc and cc; see | and cc; see also doc/FAQ_HPUX
| | | |(<tgl@sss.pgh.pa.us>), 11.00, |also doc/FAQ_HPUX| IRIX MIPS 7.3 2002-10-27, Ian Barwick (<barwick@gmx.net>) Irix64 Komma
| | | |11.11, 32 & 64 bit, Giles Lean | | 6.5
|________|___________|_______|(<giles@nemeton.com.au>)_________|_________________| Linux Alpha 7.3 2002-10-28, Magnus Naeslund (<mag@fbab.net>)
|IRIX |MIPS |7.3 |2002-10-27, Ian Barwick |Irix64 Komma 6.5 | 2.4.19-pre6
|________|___________|_______|(<barwick@gmx.net>)______________|_________________| Linux armv4l 7.2 2001-12-10, Mark Knox (<segfault@hardline.org>) 2.2.x
|Linux |Alpha |7.3 |2002-10-28, Magnus Naeslund |2.4.19-pre6 | Linux MIPS 7.2 2001-11-15, Hisao Shibuya (<shibuya@alpha.or.jp>)
|________|___________|_______|(<mag@fbab.net>)_________________|_________________| 2.0.x; Cobalt Qube2
|Linux |armv4l |7.2 |2001-12-10, Mark Knox |2.2.x | Linux PlayStation 2 7.3 2002-11-19, Permaine Cheung
|________|___________|_______|(<segfault@hardline.org>)________|_________________| <pcheung@redhat.com>) #undef HAS_TEST_AND_SET, remove slock_t typedef
|Linux |MIPS |7.2 |2001-11-15, Hisao Shibuya |2.0.x; Cobalt | Linux PPC74xx 7.3 2002-10-26, Tom Lane (<tgl@sss.pgh.pa.us>) bye
|________|___________|_______|(<shibuya@alpha.or.jp>)__________|Qube2____________| 2.2.18; Apple G3
|Linux |PlayStation|7.2 |2001-12-12, Permaine Cheung |#undef | Linux S/390 7.3 2002-11-22, Permaine Cheung <pcheung@redhat.com>) both
| |2 | |<pcheung@redhat.com>) |HAS_TEST_AND_SET,| s390 and s390x (32 and 64 bit)
|________|___________|_______|_________________________________|slock_t__________| Linux Sparc 7.3 2002-10-26, Doug McNaught (<doug@mcnaught.org>) 3.0
|Linux |PPC74xx |7.3 |2002-10-26, Tom Lane |bye 2.2.18; Apple| Linux x86 7.3 2002-10-26, Alvaro Herrera (<alvherre@dcc.uchile.cl>)
|________|___________|_______|(<tgl@sss.pgh.pa.us>)____________|G3_______________| 2.4
|Linux |S/390 |7.2 |2001-12-12, Permaine Cheung | | MacOS X PPC 7.3 2002-10-28, 10.1, Tom Lane (<tgl@sss.pgh.pa.us>),
|________|___________|_______|<pcheung@redhat.com>)____________|_________________| 10.2.1, Adam Witney (<awitney@sghms.ac.uk>)
|Linux |Sparc |7.3 |2002-10-26, Doug McNaught |3.0 | NetBSD Alpha 7.2 2001-11-20, Thomas Thai (<tom@minnesota.com>) 1.5W
|________|___________|_______|(<doug@mcnaught.org>)____________|_________________| NetBSD arm32 7.3 2002-11-19, Patrick Welche (<prlw1@newn.cam.ac.uk>)
|Linux |x86 |7.3 |2002-10-26, Alvaro Herrera |2.4 | 1.6
|________|___________|_______|(<alvherre@dcc.uchile.cl>)_______|_________________| NetBSD m68k 7.0 2000-04-10, Henry B. Hotz (<hotz@jpl.nasa.gov>) Mac
|MacOS X |PPC |7.3 |2002-10-28, 10.1, Tom Lane | | 8xx
| | | |(<tgl@sss.pgh.pa.us>), 10.2.1, | | NetBSD MIPS 7.2.1 2002-06-13, Warwick Hunter (<whunter@agile.tv>)
| | | |Adam Witney | | 1.5.3
|________|___________|_______|(<awitney@sghms.ac.uk>)__________|_________________| NetBSD PPC 7.2 2001-11-28, Bill Studenmund (<wrstuden@netbsd.org>) 1.5
|NetBSD |Alpha |7.2 |2001-11-20, Thomas Thai |1.5W | NetBSD Sparc 7.2 2001-12-03, Matthew Green (<mrg@eterna.com.au>) 32-
|________|___________|_______|(<tom@minnesota.com>)____________|_________________| and 64-bit builds
|NetBSD |arm32 |7.3 |2002-11-19, Patrick Welche |1.6 | NetBSD VAX 7.1 2001-03-30, Tom I. Helbekkmo (<tih@kpnQwest.no>) 1.5
|________|___________|_______|(<prlw1@newn.cam.ac.uk>)_________|_________________| NetBSD x86 7.3 2002-11-14, Patrick Welche (<prlw1@newn.cam.ac.uk>) 1.6
|NetBSD |m68k |7.0 |2000-04-10, Henry B. Hotz |Mac 8xx | OpenBSD Sparc 7.3 2002-11-17, Christopher Kings-Lynne
|________|___________|_______|(<hotz@jpl.nasa.gov>)____________|_________________| (<chriskl@familyhealth.com.au>) 3.2
|NetBSD |MIPS |7.2.1 |2002-06-13, Warwick Hunter |1.5.3 | OpenBSD x86 7.3 2002-11-14, 3.1 Magnus Naeslund (<mag@fbab.net>), 3.2
|________|___________|_______|(<whunter@agile.tv>)_____________|_________________| Christopher Kings-Lynne (<chriskl@familyhealth.com.au>)
|NetBSD |PPC |7.2 |2001-11-28, Bill Studenmund |1.5 | SCO OpenServer 5 x86 7.3.1 2002-12-11, Shibashish Satpathy
|________|___________|_______|(<wrstuden@netbsd.org>)__________|_________________| (<shib@postmark.net>) 5.0.4, gcc; see also doc/FAQ_SCO
|NetBSD |Sparc |7.2 |2001-12-03, Matthew Green |32- and 64-bit | Solaris Sparc 7.3 2002-10-28, Andrew Sullivan
|________|___________|_______|(<mrg@eterna.com.au>)____________|builds___________| (<andrew@libertyrms.info>) Solaris 7 and 8; see also doc/FAQ_Solaris
|NetBSD |VAX |7.1 |2001-03-30, Tom I. Helbekkmo |1.5 | Solaris x86 7.3 2002-11-20, Martin Renters (<martin@datafax.com>) 5.8;
|________|___________|_______|(<tih@kpnQwest.no>)______________|_________________| see also doc/FAQ_Solaris
|NetBSD |x86 |7.3 |2002-11-14, Patrick Welche |1.6 | SunOS 4 Sparc 7.2 2001-12-04, Tatsuo Ishii (<t-ishii@sra.co.jp>)
|________|___________|_______|(<prlw1@newn.cam.ac.uk>)_________|_________________| Tru64 UNIX Alpha 7.3 2002-11-05, Alessio Bragadini
|OpenBSD |Sparc |7.3 |2002-11-17, Christopher Kings- |3.2 | (<alessio@albourne.com>)
| | | |Lynne | | UnixWare x86 7.3 2002-11-01, 7.1.3 Larry Rosenman (<ler@lerctr.org>),
|________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________| 7.1.1 and 7.1.2(8.0.0) Olivier Prenant (<ohp@pyrenet.fr>) see also
|OpenBSD |x86 |7.3 |2002-11-14, 3.1 Magnus Naeslund | | doc/FAQ_SCO
| | | |(<mag@fbab.net>), 3.2 Christopher| | Windows x86 7.3 2002-10-29, Dave Page (<dpage@vale-housing.co.uk>),
| | | |Kings-Lynne | | Jason Tishler (<jason@tishler.net>) with Cygwin; see doc/FAQ_MSWIN
|________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________| Windows x86 7.3 2002-11-05, Dave Page (<dpage@vale-housing.co.uk>)
|Solaris |Sparc |7.3 |2002-10-28, Andrew Sullivan |Solaris 7 & 8; | native is client-side only; see documentation
| | | |(<andrew@libertyrms.info>) |see also doc/ |
|________|___________|_______|_________________________________|FAQ_Solaris______| Unsupported Platforms: The following platforms are either known not to
|Solaris |x86 |7.2 |2001-11-28, Martin Renters |2.8; see also | work, or they used to work in a previous release and we did not
|________|___________|_______|(<martin@datafax.com>)___________|doc/FAQ_Solaris__| receive explicit confirmation of a successful test with version 7.4 at
|SunOS 4 |Sparc |7.2 |2001-12-04, Tatsuo Ishii (<t- | | the time this list was compiled. We include these here to let you know
|________|___________|_______|ishii@sra.co.jp>)________________|_________________| that these platforms *could* be supported if given some attention.
|Tru64 |Alpha |7.3 |2002-11-05, Alessio Bragadini | |
|UNIX____|___________|_______|(<alessio@albourne.com>)_________|_________________| OS Processor Version Reported Remarks
|UnixWare|x86 |7.3 |2002-11-01, 7.1.3 Larry Rosenman |see also doc/ | BeOS x86 7.2 2001-11-29, Cyril Velter (<cyril.velter@libertysurf.fr>)
| | | |(<ler@lerctr.org>), 7.1.1 and |FAQ_SCO | needs updates to semaphore code
| | | |7.1.2(8.0.0) Olivier Prenant | | DG/UX 5.4R4.11 m88k 6.3 1998-03-01, Brian E Gallew (<geek+@cmu.edu>)
|________|___________|_______|(<ohp@pyrenet.fr>)_______________|_________________| no recent reports
|Windows |x86 |7.3 |2002-10-29, Dave Page |with Cygwin; see | MkLinux DR1 PPC750 7.0 2001-04-03, Tatsuo Ishii (<t-ishii@sra.co.jp>)
| | | |(<dpage@vale-housing.co.uk>), |doc/FAQ_MSWIN | 7.1 needs OS update?
| | | |Jason Tishler | | NeXTSTEP x86 6.x 1998-03-01, David Wetzel (<dave@turbocat.de>) bit rot
|________|___________|_______|(<jason@tishler.net>)____________|_________________| suspected
|Windows |x86 |7.3 |2002-11-05, Dave Page |native is client-| QNX 4 RTOS x86 7.2 2001-12-10, Bernd Tegge (<tegge@repas-aeg.de>)
| | | |(<dpage@vale-housing.co.uk>) |side only; see | needs updates to semaphore code; see also doc/FAQ_QNX4
| | | | |Administrator's | QNX RTOS v6 x86 7.2 2001-11-20, Igor Kovalenko
|________|___________|_______|_________________________________|Guide____________| (<Igor.Kovalenko@motorola.com>) patches available in archives, but too
late for 7.2
Unsupported Platforms: The following platforms are either known not to work, or System V R4 m88k 6.2.1 1998-03-01, Doug Winterburn
they used to work in a previous release and we did not receive explicit (<dlw@seavme.xroads.com>) needs new TAS spinlock code
confirmation of a successful test with version 7.3 at the time this list was System V R4 MIPS 6.4 1998-10-28, Frank Ridderbusch
compiled. We include these here to let you know that these platforms *could* be (<ridderbusch.pad@sni.de>) no recent reports
supported if given some attention. Ultrix MIPS 7.1 2001-03-26 TAS spinlock code not detected
_____________________________________________________________________________ Ultrix VAX 6.x 1998-03-01
|OS__________|Processor|Version|Reported_______________________|Remarks_______|
|BeOS |x86 |7.2 |2001-11-29, Cyril Velter |needs updates |
| | | |(<cyril.velter@libertysurf.fr>)|to semaphore |
|____________|_________|_______|_______________________________|code__________|
|DG/UX |m88k |6.3 |1998-03-01, Brian E Gallew |no recent |
|5.4R4.11____|_________|_______|(<geek+@cmu.edu>)______________|reports_______|
|MkLinux DR1 |PPC750 |7.0 |2001-04-03, Tatsuo Ishii (<t- |7.1 needs OS |
|____________|_________|_______|ishii@sra.co.jp>)______________|update?_______|
|NeXTSTEP |x86 |6.x |1998-03-01, David Wetzel |bit rot |
|____________|_________|_______|(<dave@turbocat.de>)___________|suspected_____|
|QNX 4 RTOS |x86 |7.2 |2001-12-10, Bernd Tegge |needs updates |
| | | |(<tegge@repas-aeg.de>) |to semaphore |
| | | | |code; see also|
|____________|_________|_______|_______________________________|doc/FAQ_QNX4__|
|QNX RTOS v6 |x86 |7.2 |2001-11-20, Igor Kovalenko |patches |
| | | |(<Igor.Kovalenko@motorola.com>)|available in |
| | | | |archives, but |
| | | | |too late for |
|____________|_________|_______|_______________________________|7.2___________|
|SCO |x86 |6.5 |1999-05-25, Andrew Merrill |7.2 should |
|OpenServer 5| | |(<andrew@compclass.com>) |work, but no |
| | | | |reports; see |
| | | | |also doc/ |
|____________|_________|_______|_______________________________|FAQ_SCO_______|
|System V R4 |m88k |6.2.1 |1998-03-01, Doug Winterburn |needs new TAS |
|____________|_________|_______|(<dlw@seavme.xroads.com>)______|spinlock_code_|
|System V R4 |MIPS |6.4 |1998-10-28, Frank Ridderbusch |no recent |
|____________|_________|_______|(<ridderbusch.pad@sni.de>)_____|reports_______|
|Ultrix |MIPS |7.1 |2001-03-26 |TAS spinlock |
| | | | |code not |
|____________|_________|_______|_______________________________|detected______|
|Ultrix______|VAX______|6.x____|1998-03-01_____________________|______________|
doc/src/sgml/installation.sgml
View file @ 5ba1fab5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.145 2003/09/27 14:06:21 momjian Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.146 2003/10/04 03:14:13 momjian Exp $ -->
<chapter id="installation"> <chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]> <title><![%standalone-include[<productname>PostgreSQL</>]]>
...@@ -1169,9 +1169,11 @@ All of PostgreSQL is successfully made. Ready to install. ...@@ -1169,9 +1169,11 @@ All of PostgreSQL is successfully made. Ready to install.
optimum performance. To achieve optimum performance, several server optimum performance. To achieve optimum performance, several server
variables must be adjusted, the two most common being variables must be adjusted, the two most common being
<varname>shared_buffers</varname> and <varname> sort_mem</varname> <varname>shared_buffers</varname> and <varname> sort_mem</varname>
mentioned in <xref linkend="runtime-config-resource-memory">. Other mentioned in <![%standalone-include[the documentation]]>
parameters in <xref linkend="runtime-config-resource"> also affect <![%standalone-ignore[<xref linkend="runtime-config-resource-memory">]]>.
performance. Other parameters in <![%standalone-include[the documentation]]>
<![%standalone-ignore[<xref linkend="runtime-config-resource">]]>
also affect performance.
</para> </para>
</sect2> </sect2>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment