Movatterモバイル変換

Note

This is the lastPostgres Pro release that supports Ubuntu 20.04. Starting from the next release, this operating system will no longer be supported.

Note

The nextPostgres Pro release will be the last to support Ubuntu 24.10.

• Red Hat Enterprise Linux (RHEL) systems and its derivatives: CentOS 8, Rocky Linux 8/9, Red Hat Enterprise Linux 8/9, Oracle Linux 8/9, ROSA Chrome 2021.2, Red OS Murom 7.3/8, AlmaLinux 9

• Debian-based systems: Debian 11/12, Ubuntu 20.04/22.04/24.04/24.10/25.04, Astra Linux 1.7/1.8/3.8

• ALT 10/11, ALT SP Release 10

• SUSE Linux Enterprise Server (SLES) 15

• MosOS 15

• Linux systems for Elbrus CPU architecture: ALT 9/10 for e2kv3/e2kv4, ALT 8.2 SP for e2kv3/e2kv4, ALT SP Release 10, Astra Linux Leningrad 8.1

• Linux systems for ARM architecture: ALT 9/10/11, ALT SP 8.2 and higher, Astra Linux Novorossiysk, Debian 10/11, Red OS Murom 7.3/8, RHEL 8/9, Ubuntu 20.04/22.04/24.04

Note

Postgres Pro binary packages rely on thetzdata library provided by the operating system, so you must ensure that the latest available version is installed. Iftzdata is outdated, the time in your database may be incorrect.

1. Contact thePostgres Pro Standard support team to download thepgpro-repo-add.sh Bash script. The support team will also provide you with the credentials to access the repository.

   This script adds the repository so that the package manager of your operating system can use it.

2. Make sure that thewget utility is installed and can access the Internet.

   The script requireswget and the Internet access to check the validity of the credentials when adding the repository.

   Note

   It is not possible to use a SOCKS5 proxy for accessing the Internet aswget does not support this type of proxy.

3. (Optional) Examine the content of the script, if necessary.

4. Run the script asroot (e. g. usingsudo).

5. When prompted, enter the access credentials.

   Important

   If no credentials are provided or they are invalid, the script will offer to add the repository without credentials.

   If you proceed without credentials, you will be required to manually provide the credentials later in order to access the repository.

1. Add the package repository required for your operating system.

2. Install thepostgrespro-std-17 package. It will bring all the required components via dependencies, create the default database, start the database server, as well as enable server autostart at system boot and make all the provided programs available inPATH.

Note

By default, the database configuration is set for thePostgres Pro product being installed. If you need your database configured for a different product, choosecustom installation and use thetune argument of thepg-setup initdb command.

1. Add the package repository required for your operating system.

2. ChoosePostgres Pro packages required for your purposes and install them using the standard installation commands for your Linux distribution. The available packages are listed inTable 16.1.

   As a result, all files get installed into the/opt/pgpro/std-17 directory.

3. Runpg-wrapper as root to make the installed client and server programs available viaPATH and addSQL man pages to the man page configuration file. This utility is provided in thepostgrespro-std-17-client package.

   /opt/pgpro/std-17/bin/pg-wrapper links update

   For details on how to handle possible conflicts, seepg-wrapper description.

4. If you chose to install thepostgrespro-std-17-server package, make sure to complete the following server setup:

   1. Create the default database by running the helper scriptpg-setup as root with theinitdb option:

      /opt/pgpro/std-17/bin/pg-setup initdb [--tune=conf] [initdb_options]

      where:

      • thetune command-line argument sets the database configuration.

      • initdb_options are regularinitdb options.

      Note

      By default,pg-setup initializes the database cluster with checksums enabled. If this is not what you expect, specify the--no-data-checksums.

      Thepg-setup script performs database administration operations as userpostgres. If you do not specify anyinitdb options, the default database is created in the/var/lib/pgpro/std-17/data directory, using localization settings specified in theLANG environment variable for the current session. All theLC_* environment variables are ignored.

      Since the default database is created using thepg-setup script, the path to its data directory is stored in the/etc/default/postgrespro-std-17 file. All the subsequentpg-setup commands, as well as any commands that managePostgres Pro service, affect this database only. In this file, you can also change the value ofPG_OOM_ADJUST_VALUE for postmaster child processes (seeSection 17.4.4 for details).

   2. Start the server by runningpg-setup as root, as follows:

      /opt/pgpro/std-17/bin/pg-setup service start

      Like vanillaPostgreSQL,Postgres Pro server runs on behalf of thepostgres user.

      Note

      By default, automatic server startup is disabled, so you can manually control the database recovery after a system reboot. Optionally, you can configure thePostgres Pro server to start automatically. For details, seeSection 16.1.4.2.

The table below lists all the availablePostgres Pro Standard packages.

Also, Postgres Pro includes libraries and utilities required for the Postgres Pro server and provided packages. These packages are only provided for the distributions that don't include the required versions of these libraries.

Besides, there are separate packages providing several external modules that have been pre-built for compatibility with Postgres Pro Standard:

Additionally,Postgres Pro provides separate packages with debug information for some operating systems:

Server installations require at least the following packages:

To use additionalPostgres Pro extensions, you must also install thepostgrespro-std-17-contrib package. On Debian-based systems,postgrespro-std-17-server package depends onpostgrespro-std-17-contrib package, so the latter must always be installed together with the server.

For client installations, it is usually enough to install thepostgrespro-std-17-client andpostgrespro-std-17-libs packages. If you use custom applications and do not need standard client utilities such aspsql, you can install thepostgrespro-std-17-libs package only.

Development workstations require at least the following packages:

You may also want to install and configure the server with a test database on development systems. For details on additional configuration that may be required,Section 16.1.5.

If you are running a custom installation, automatic server startup is disabled by default. Once the default database is created, you can configure the server to start automatically upon system boot using service management solutions available in your operating system or third-party high-availability software. To facilitate this task,postgrespro-std-17-server package provides thepg-setup script, which is installed in the/opt/pgpro/std-17/bin directory.

To enable server autostart, run thepg-setup script with the following options:

pg-setup service enable

If required, you can disable server autostart using the same script:

pg-setup service disable

Alternatively, you can use system service management solutions directly by running the autostart scripts for SysV-styleinit.d andsystemd provided in thepostgrespro-std-17-server package. Depending on your Linux distribution,Postgres Pro supports different service management solutions:

To usesystemd for automatic server startup, run the following command:

systemctl enable postgrespro-std-17

To use SysV-styleinit.d script:

• Install LLVM development package and Clang compiler. You must choose the packages of the same version that was used for thepostgrespro-std-17-jit to be installed on the server. To determine the required version for the currentPostgres Pro release, check theCLANG value in the/opt/pgpro/std-17/lib/pgxs/src/Makefile.global file.

• When runningmake ormake install commands, specify thewith-llvm=yes option to compile and install bitcode files for your extension. By default, bitcode compilation is disabled as it depends on Clang compiler availability.

To usePostgres Pro server with a client program provided with a third-party product, you can install the version ofPostgreSQL libraries that was used to compile this program. For example, if this program is provided with vanillaPostgreSQL, you may need to install thelibpq orpostgresql-libs packages available for your Linux distribution. In this case, the program may not be able to use some new features ofPostgres Pro server, but it is probably not designed to use them anyway.

If you prefer to usePostgres Pro libraries with a third-party program, or would like to enable support for a new feature that does not require client application change, such asSCRAM authentication, you can recompile your program withPostgres Pro libraries.

If you are creating.rpm or.deb packages for your program, it is recommended to do the following:

Thus, you can ensure that your package build process calls the right version ofpg_config whenever the source package is rebuilt.

1. Install and configurePostgres Pro as explained inSection 16.1.3 orSection 16.1.4.

2. Once the first default database is created, runinitdb specifying the path to a different data directory and any other parameters required to initialize another server instance.

3. Specify different ports for your server instances in the correspondingpostgresql.conf files to avoid conflicts.

4. If required, configure automatic server startup, as follows:

   1. Create a copy of/etc/init.d/postgrespro-std-17 or/lib/systemd/system/postgrespro-std-17.service with a different name, specifying the path to the data directory.

   2. Enable automatic server startup using the provided autostart scripts for your system service management facility instead ofpg-setup, as described inSection 16.1.4.2. Make sure to use the renamed copies of the scripts you created in step 1.

• PGDATA directory that stores main cluster data, usually located in/var/lib/pgpro/std-17/data unless you specified another directory ininitdb options

• Paths to createdtablespaces