Installing extensions v6.5.0

Postgres extensions provide SQL objects, such as functions, datatypes, and, optionally, one or more shared libraries.

See PGD compatibility with extensions for which extensions PGD supports and on which Postgres versions.

If you deployed PGD using Trusted Postgres Architect, configure extensions using that tool. For details, see Adding Postgres extensions.

Making extension packages available on every node

Before you configure or install an extension, make sure its package is on every node in the cluster.

1. Find the package that provides the extension for your platform and Postgres distribution. Package names typically follow the same pattern as the database and PGD packages you installed in Installing the database and PGD software, for example edb-as$PG_VERSION-pgaudit or postgresql$PG_VERSION-pgvector. See Postgres extensions for the specific package names.

2. On each node, install the package with your package manager.

   → WrapCopy

   # Debian/Ubuntu
   sudo apt install -y <package-name>

   → WrapCopy

   # CentOS/RHEL
   sudo dnf install -y <package-name>

3. Repeat these steps on every node before you continue.

Configuring shared_preload_libraries

If an extension provides a shared library, include this library in the shared_preload_libraries configuration parameter before you install the extension.

shared_preload_libraries consists of a comma-separated list of extension names. It must include bdr. The order in which you specify other extensions generally doesn't matter.

Configure shared_preload_libraries on all nodes in the cluster before installing the extension with CREATE EXTENSION, then restart Postgres to activate the new configuration.

See also Postgres settings.

Installing the extension

Install the extension with the CREATE EXTENSION command. You only need to do run the command on one node in the cluster. PGD's DDL replication propagates it to all other nodes.

CREATE EXTENSION <extension-name>;