The following PostgreSQL extensions are available, and can be enabled with the CREATE EXTENSION command.

Please note that some of the extensions have dependencies and they need to be created in the proper order. Also some extensions may require disconnecting the client connection and reconnecting before they are fully available.

List of supported extensions:

  • address_standardizer
  • address_standardizer_data_us
  • btree_gin
  • btree_gist
  • chkpass
  • citext
  • cube
  • dblink
  • dict_int
  • earthdistance
  • fuzzystrmatch
  • hstore
  • intagg
  • intarray
  • isn
  • ltree
  • pg_buffercache
  • pg_partman (PostgreSQL 9.5, 9.6 and 10) 
  • pg_prometheus (PostgreSQL 10) 
  • pg_repack (PostgreSQL 10+)
  • pg_stat_statements
  • pg_trgm
  • pgcrypto
  • pgrouting
  • pgrowlocks
  • pgstattuple
  • plcoffee
  • plls
  • plperl (PostgreSQL 9.5+)
  • plv8  (PostgreSQL 9.5, 9.6 and 10) 
  • postgis
  • postgis_sfcgal
  • postgis_tiger_geocoder
  • postgis_topology
  • postgis_legacy (see note below)
  • postgres_fdw
  • sslinfo
  • tablefunc
  • timescaledb (PostgreSQL 10)
  • tsearch2
  • unaccent
  • uuid-ossp

The postgis_legacy extension is not packaged or supported as an extension by the PostGIS project, the extension package is provided by Aiven for Aiven users.

Based on support requests, we may also install additional extension related files for your database. When requesting things not on the pre-approved list through a support ticket, be sure to remember to specify to which database service and to which particular user database you'd like to see us install them.

"Untrusted" language extensions such as plpythonu cannot be supported as they would compromise our ability to guarantee the highest possible service level.

If you have some other extensions you'd like to be supported, please give us a heads up on what you'd like to see in the future.

Did this answer your question?