Performing an RPM Installation

For detailed information about creating and using EnterpriseDB repositories to install Advanced Server or its supporting components, please see the EDB Postgres Advanced Server Installation Guide, available at:

https://www.enterprisedb.com/resources/product-documentation

Before installing PgBouncer, you must:

Install the epel-release package:

yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

Note

You may need to enable the [extras] repository definition in the CentOS-Base.repo file (located in /etc/yum.repos.d).

You must also have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit:

After receiving your repository credentials you can:

  1. Create the repository configuration file.

  2. Modify the file, providing your user name and password.

  3. Install edb-pgbouncer17.

Creating a Repository Configuration File

To create the repository configuration file, assume superuser privileges, and invoke the following command:

yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm

The repository configuration file is named edb.repo. The file resides in /etc/yum.repos.d.

Modifying the file, providing your user name and password

After creating the edb.repo file, use your choice of editor to ensure that the value of the enabled parameter is 1, and replace the username and password placeholders in the baseurl specification with the name and password of a registered EnterpriseDB user.

[edb]
name=EnterpriseDB RPMs $releasever - $basearch
baseurl=https://<username>:<password>@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY

Installing PgBouncer

After saving your changes to the configuration file, you can use the yum install command to install PgBouncer. For example, the following command installs PgBouncer:

yum install edb-pgbouncer17

When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter y, and press Return to continue.

During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve.