Supported Extensions
The following table lists the extensions supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the extensions supported by your DB instance.
The extensions mysql_fdw, dblink, pgsql-ogr-fdw, postgres_fdw, and tds_fdw are used to access data stored in remote database servers. Before using any of them, ensure that the server IP addresses of the two DB instances are in the same VPC and subnet.
Extension Name |
PostgreSQL 9.5 |
PostgreSQL 9.6 |
PostgreSQL 10 |
PostgreSQL 11 |
PostgreSQL 12 |
PostgreSQL 13 |
---|---|---|---|---|---|---|
address_standardizer |
2.5.1 |
2.5.1 |
2.5.1 |
2.5.1 |
3.0.0 |
3.1.0 |
address_standardizer_data_us |
2.5.1 |
2.5.1 |
2.5.1 |
2.5.1 |
3.0.0 |
3.1.0 |
auth_delay |
- |
- |
- |
- |
1.0 |
1.0 |
btree_gin |
1.0 |
1.0 |
1.2 |
1.3 |
1.3 |
1.3 |
btree_gist |
1.1 |
1.2 |
1.5 |
1.5 |
1.5 |
1.5 |
citext |
1.1 |
1.3 |
1.4 |
1.5 |
1.6 |
1.6 |
cube For details, see cube. |
1.0 |
1.2 |
1.2 |
1.4 |
1.4 |
1.4 |
dblink |
1.1 |
1.2 |
1.2 |
1.2 |
1.2 |
1.2 |
dict_int |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
dict_xsyn |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
earthdistance For details, see earthdistance. |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.1 |
fuzzystrmatch |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.1 |
hll |
2.12 |
2.12 |
2.12 |
2.12 |
2.14 |
2.15.1 |
hstore |
1.3 |
1.4 |
1.4 |
1.5 |
1.6 |
1.7 |
intagg |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.1 |
intarray |
1.0 |
1.2 |
1.2 |
1.2 |
1.2 |
1.3 |
isn |
1.0 |
1.1 |
1.1 |
1.2 |
1.2 |
1.2 |
ltree |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.2 |
oracle_fdw |
- |
- |
1.1 |
1.1 |
1.1 |
2.3.0 |
orafce |
3.8 |
3.8 |
3.8 |
3.8 |
3.8 |
3.14.0 |
pgAudit |
- |
- |
- |
- |
1.6.2 |
1.6.2 |
pg_hint_plan |
1.1.5 |
1.2.0 |
1.3.0 |
1.3.0 |
- |
1.3.7 |
pg_jieba |
1.1.0 |
1.1.0 |
1.1.0 |
1.1.0 |
1.1.0 |
2.0.1 |
pg_pathman |
1.5 |
1.5 |
1.5 |
1.5 |
1.5 |
1.5.12 |
pg_repack |
1.4.6 |
1.4.6 |
1.4.6 |
1.4.6 |
1.4.6 |
1.4.6 |
pgrouting |
- |
- |
- |
3.1.0 |
3.1.0 |
3.1.3 |
pg_stat_statements |
1.3 |
1.4 |
1.6 |
1.6 |
1.7 |
1.8 |
pg_trgm |
1.1 |
1.3 |
1.3 |
1.4 |
1.4 |
1.5 |
pgcrypto |
1.2 |
1.3 |
1.3 |
1.3 |
1.3 |
1.3 |
pgstattuple |
- |
- |
1.5 |
1.5 |
1.5 |
1.5 |
plpgsql For details, see plpgsql. |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
postgis For details, see postgis. |
2.5.1 |
2.5.1 |
2.5.1 |
2.5.1 |
3.0.0 |
3.1.0 |
postgres_fdw |
- |
- |
1.0 |
1.0 |
1.0 |
1.0 |
postgis_raster |
Integrated to postgis |
Integrated to postgis |
Integrated to postgis |
Integrated to postgis |
3.0.0 |
3.1.0 |
postgis_sfcgal |
1.3.9 |
1.3.9 |
1.3.9 |
1.3.9 |
1.3.9 |
3.1.0 |
postgis_tiger_geocoder |
2.5.1 |
2.5.1 |
2.5.1 |
2.5.1 |
3.0.0 |
3.1.0 |
postgis_topology |
2.5.1 |
2.5.1 |
2.5.1 |
2.5.1 |
3.0.0 |
3.1.0 |
tablefunc |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
tds_fdw |
- |
- |
- |
2.0.1 |
2.0.1 |
2.0.2 |
TimescaleDB For details, see TimescaleDB. |
- |
1.3.2 |
1.3.2 |
1.3.2 |
1.7.0 |
2.1.0 |
unaccent |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.1 |
uuid-ossp |
1.0 |
1.1 |
1.1 |
1.1 |
1.1 |
1.1 |
wal2json |
- |
- |
- |
2.3 |
2.3 |
2.3 |
zhparser |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
1.0 |
Extension Description
- postgis
- Creating postgis_topology and postgis_tiger_geocoder will change the search_path settings. However, this change will not take effect for established connections. To use the two extensions, re-establish a connection to update the search_path settings.
- plpgsql
plpgsql 1.0 provides the SQL procedural language and is installed by default.
- earthdistance
To install the earthdistance extension, you must install the cube extension first.
- cube
If the earthdistance extension has been installed, deleting the cube extension will cause the earthdistance extension to be unavailable.
- TimescaleDB
The TimescaleDB extension of RDS for PostgreSQL supports only the features of the Apache protocol. It does not support the features of the TSL protocol. For details, see TimescaleDB Apache 2 and TimescaleDB Community Edition.
- wal2json
This extension is a logical replication extension. You can directly use it without installing it through control_extension.
This extension cannot be queried from the pg_available_extensions view. You can run the following statement to check whether wal2json is supported. If no error is reported, wal2json is supported.
select pg_create_logical_replication_slot('tst_wal2json', 'wal2json');
After the statement is executed successfully, delete the slot to prevent stacked WAL logs.
select pg_drop_replication_slot('tst_wal2json');
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.