For Red Hat Enterprise Linux and its derivatives, such as CentOS, Oracle Linux, and Rosa Enterprise Linux Server, Postgres Pro distribution is split into the following packages:

For server installations, install at least the following packages:

To use additional Postgres Pro extensions, you must also install the postgrespro96-contrib package.

By default, all files are installed into the /usr/pgpro-9.6 directory. Make sure /usr/pgpro-9.6/bin is added to your PATH environment variable.

Installation of the postgrespro96-server package does not create the default database. It only creates the postgres system user that owns database files and server processes.

To create the default database, run the helper script pg-setup as root:

/usr/pgpro-9.6/bin/pg-setup initdb

In this case, the peer authentication method will be used for all local connections, while the ident method will be used for all network connections. For details on available authentication methods, see Section 19.3.

To run several instances of Postgres Pro server with different data directories, create a copy or a symlink of /etc/init.d/postgresql with a different name, create the corresponding /etc/sysconfig files and symlinks in runlevel directories.

If required, you can install vanilla PostgreSQL, Postgres Pro, and Postgres Pro Enterprise on the same system simultaneously.

The name of sysconfig file read by init.d script is derived from its own name.

For Debian-based operating systems (Debian, Ubuntu, Astra Linux), Postgres Pro is split into following packages:

Server installations require postgrespro-9.6 package (which depends on postgrespro-contrib-9.6). Other server-related packages, such as the ones for PL languages or pg_probackup, are optional.

Client installations need only postgrespro-libpq5 and postgrespro-client-9.6 packages. If you use custom applications and do not need standard clients such as psql, you can install the postgrespro-libpq5 package only.

Development files on Debian are split into the following packages:

Debian database server packages create the default database at the moment of server installation, and allow to create additional ones, called clusters using pg_createcluster script. All these clusters are managed using system service management facilities (SysVinit in older distributions, systemd in newer ones).

pg_createcluster also allows to import existing databases into Debian-specific service management system. It tries to automatically enable SSL on the newly created cluster, but can do so only if the postgres user is a member of ssl-cert group and there is valid certificate in /etc/ssl/certs.

Postgres Pro distribution for Debian-based systems uses a non-standard directory layout for the database cluster. By default, Postgres Pro keeps configuration files and data in the same directory. However, Debian policy requires configuration files to be stored under /etc. Thus, on Debian-based systems, the PGDATA parameter always points to a subdirectory under /etc, where only postgresql.conf, pg_hba.conf and a few other configuration files are stored. The actual location of data is determined by the data_directory option in postgresql.conf.

The postgrespro-common and postgrespro-client-common packages provide a complex infrastructure that allows running several versions of PostgreSQL, Postgres Pro and Postgres Pro Enterprise servers simultaneously, thus enabling smooth database upgrades.

For more information about Debian-specific infrastructure, see the following manual pages: pg_createcluster(8), pg_ctlcluster(8), pg_conftool(1), postgresql-common(5), postgresqlrc(5) and user_clusters(5).

Debian provides the script pg_wrapper(1) to invoke client binaries for correct version of your PostgreSQL-based product. It is linked as /usr/bin/psql, /usr/bin/pg_dump, etc. If several PostgreSQL-based products are installed, it invokes the most recent binaries unless explicitly configured to do the opposite.

For ALT Linux, Postgres Pro is split into the following packages:

All packages containing binary files have the corresponding -debuginfo packages.

For server installations, you need postgrespro-9.6-server. For a minimal client installation, only the libpq5.9 package is required. postgrespro-9.6 is typically needed on clients.

pg_config utility is only shipped as part of postgrespro-9.6-devel package, so you need to install this package if you are going to compile client programs that use pg_config in the build process.

On ALT Linux, you can only have a single PostgreSQL installation on your system at a time. If you are installing a newer version over the old one, new binaries replace the old ones. To perform database upgrade using pg_upgrade utility, you need both new and old postgres executable files. So, pre-installation script copies the existing postgres binary and libpq shared library into /usr/lib64/pgsql/9.6/backup. Use this directory name as an argument of the pg_upgrade -b option.

For SUSE systems, Postgres Pro is split into following packages:

Server installations require postgrespro96-server, postgrespro96, and postgrespro96-libs packages. To use additional Postgres Pro extensions, you must also install the postgrespro96-contrib package.

To start Postgres Pro server after installation of the server package, run the following command as root:

service postgresql start

The default database in SUSE is created upon the first start of service. You can customize its location, locale, and other parameters in /etc/sysconfig/postgrespro.

On SUSE systems, you cannot install several versions of client programs simultaneously.