VMware Postgres is currently supported only on Red Hat Enterprise Linux (RHEL) version 8, RHEL version 9, and Ubuntu 22.04. This applies both to the core database software, as well as client components such as ODBC and JDBC.
Each RPM file included with VMware Postgres automatically installs additional operating-system package dependencies as needed. However, no Extra Packages for Enterprise Linux (EPEL) repository packages are required for VMware Postgres.
Network connectivity is required between all PostgreSQL hosts and clients.
SELinux must either be deactivated or configured to allow unconfined access for VMware Postgres. See Deactivate or Verify SELinux Configuration.
ODBC support requires either the UnixODBC or iODBC driver manager on each client machine.
JDBC support requires Java 8 or higher on each client machine.
For all VMware Postgres host systems, SELinux must either be Disabled
or configured to allow unconfined access to VMware Postgres processes, directories, and user. This applies both to the core database software as well as components such as Patroni.
If you choose to deactivate SELinux:
As the root user, check the status of SELinux:
# sestatus
SELinuxstatus: disabled
If SELinux is not deactivated, deactivate it by editing the /etc/selinux/config
file. As root, change the value of the SELINUX
parameter in the config
file as follows:
SELINUX=disabled
If the System Security Services Daemon (SSSD) is installed on your systems, edit the SSSD configuration file and set the selinux_provider
parameter to none
to prevent SELinux-related SSH authentication denials that could occur even with SELinux deactivated. As root, edit /etc/sssd/sssd.conf
and add this parameter:
selinux_provider=none
Reboot the system to apply any changes that you made and verify that SELinux is deactivated.
If you choose to enable SELinux in Enforcing
mode, then VMware Postgres processes and users can operate successfully in the default Unconfined
context. If you require increased SELinux confinement for VMware Postgres processes and users, you must test your configuration to ensure that there are no functionality or performance impacts. See the SELinux User’s and Administrator’s Guide for detailed information about configuring SELinux and SELinux users.