Use supported extensions in FPT PostgreSQL
With built-in PostgreSQL extensions, FPT Database Engine helps you extend what your database can do to meet a wide range of operational and data processing needs, from job scheduling, auditing, and data synchronization to vector search and spatial data processing. The extensions are preinstalled at the Database Engine level, and you enable the ones you need with SQL commands.
Scope
- PostgreSQL clusters created on or after 20 November 2026 come with the extensions in the supported list preinstalled.
- PostgreSQL clusters created before 20 November 2026 do not come with these extensions preinstalled. To use these extensions on an older cluster, contact FPT Support to have it checked and get advice on a suitable option.
- Preinstalled does not mean enabled. You still run
CREATE EXTENSIONin the database where you want to use the extension.
Supported extensions
| Extension | Description | PostgreSQL 17 | PostgreSQL 16 | PostgreSQL 15 | PostgreSQL 14 |
|---|---|---|---|---|---|
pg_cron | Job scheduler that runs SQL statements on a recurring schedule inside PostgreSQL. | 1.6.8 | 1.6.8 | 1.6.8 | 1.6.8 |
pg_partman | Manages time-based or ID-based partitions and automates creating and maintaining them. | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 |
pg_partman_bgw | Background worker that runs pg_partman maintenance automatically. | 5.5.0 | 5.5.0 | 5.5.0 | 5.5.0 |
pgaudit | Records access and operations on the database for audit and compliance. | 17.1 | 16.1 | 1.7.1 | 1.6.3 |
pglogical | Logical replication between PostgreSQL databases. | 2.4.8 | 2.4.8 | 2.4.8 | 2.4.8 |
pgvector (vector) | Stores vectors and runs similarity search, for AI and RAG applications. | 0.8.7 | 0.8.7 | 0.8.7 | 0.8.7 |
PostGIS (postgis) | Stores, processes, and queries geographic (spatial) data. | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.4 |
postgis_raster | Stores and processes raster data in GIS systems. | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.4 |
postgis_tiger_geocoder | Geocoding and reverse geocoding based on US TIGER data. | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.4 |
postgis_topology | Manages and processes the topology of spatial data. | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.4 |
pgrouting | Adds route calculation and geographic network analysis on PostGIS data. | 4.0.2 | 4.0.2 | 4.0.2 | 4.0.2 |
The name in code format is the name you pass to CREATE EXTENSION. For pgvector it is vector, not pgvector.
Prerequisites
- A PostgreSQL cluster created on or after 20 November 2026.
- A connection to the database where you want the extension, through
psql, pgAdmin, or another PostgreSQL client. See Connect to database with Floating IP. - The account you connect to the database with has permission to create extensions.
- The extension listed for your PostgreSQL version in Supported extensions.
Check which extensions are available
Run this query in the target database. Every supported extension appears with its default_version. A value in installed_version means the extension is already enabled in this database.
SELECT name, default_version, installed_version, comment
FROM pg_available_extensions
ORDER BY name;
Enable an extension
Replace EXTENSION_NAME with the name from the supported list.
CREATE EXTENSION IF NOT EXISTS EXTENSION_NAME;
For example, to enable pgvector and PostGIS:
CREATE EXTENSION IF NOT EXISTS vector;
CREATE EXTENSION IF NOT EXISTS postgis;
Some extensions need another extension or a parameter configured first. Check Extensions with dependencies before you enable them.
Verify enabled extensions
SELECT extname, extversion
FROM pg_extension
ORDER BY extname;
In psql, you can run \dx instead.
An extension is enabled only in the current database. To use it in another database, connect to that database and run CREATE EXTENSION again.
Remove an extension
When you no longer need an extension, remove it with this command:
DROP EXTENSION IF EXISTS EXTENSION_NAME;
Removing an extension can affect database objects that depend on it, such as columns of type vector or geometry. Check those dependencies before you run DROP EXTENSION.
Extensions with dependencies
Some extensions depend on another extension or on an engine parameter. Enable the required extension or set the required parameter before you enable the extension you need.
| Extension | Dependency | Notes |
|---|---|---|
pg_partman_bgw | pg_partman | pg_partman_bgw is the background worker of pg_partman, not a standalone SQL extension. Run CREATE EXTENSION pg_partman and the worker is available. You do not run CREATE EXTENSION for it separately. |
pglogical | Parameter wal_level = logical | Change wal_level on the Parameters tab, as described in Configure parameters. The change requires a PostgreSQL restart to take effect, so make it off-peak to limit the impact. |
postgis_raster, postgis_tiger_geocoder, postgis_topology, pgrouting | postgis | Enable PostGIS first, then enable the extensions that depend on it. |
Common errors
| Symptom | Likely cause | What to do |
|---|---|---|
The extension does not appear in pg_available_extensions. | The cluster was created before 20 November 2026, or the extension is not supported on your PostgreSQL version. | Check the cluster's creation date and PostgreSQL version, then contact FPT Support. |
permission denied to create extension | The account does not have permission to create extensions. | Check the database permissions of the account you connect with. |
must be loaded via shared_preload_libraries | The extension needs configuration at the Database Engine level. | Contact FPT Support to check the configuration. |
extension already exists | The extension is already enabled in this database. | Confirm with the query in Verify enabled extensions. |
Next steps
- Configure parameters to set
wal_level = logicalbefore you usepglogical. - Backup & Restore overview to take a backup before you remove an extension that your data depends on.