Connect extensions to PostgreSQL TimescaleDB databases
Connect extensions to PostgreSQL TimescaleDB databases
Additional extensions can be attached to PostgreSQL TimescaleDB databases.
Connect the extension to the database
Extensions are connected to each database separately.
- In Control Panel, go to Cloud Platform → Databases.
- Open the cluster page → Databases tab → database card.
- In the Extensions block, click Add.
- Select an extension from the list and save your changes.
Dependent extensions
Some extensions depend on other extensions — they will not work unless you connect the extensions they depend on. When a dependent extension is connected to the database, the one it depends on will be automatically connected.
Dependent extension can be removed separately. To remove an extension on which another extension depends, you must first remove the dependent extension.
Dependent extensions are listed below.
- address_standardizer;
- address_standardizer_data_us;
- autoinc;
- bloom;
- btree_gin;
- btree_gist;
- citext;
- cube;
- dict_int;
- dict_xsyn;
- earthdistance, depends on the cube extension;
- fuzzystrmatch;
- hstore;
- intarray;
- ip4r;
- isn;
- jsquery;
- lo;
- ltree;
- moddatetime;
- pg_partman;
- pg_repack;
- pg_stat_kcache, depends on the pg_stat_statements extension;
- pg_stat_statements;
- pg_trgm;
- pgcrypto;
- pgrouting, depends on the postgis extension;
- pgrowlocks;
- pgTAP;
- plv8;
- postgis;
- postgis_tiger_geocoder, depends on the postgis extension;
- postgis_topology, depends on the postgis extension;
- postgres_fdw;
- prefix;
- rum;
- seg;
- tablefunc;
- unaccent;
- uuid-ossp;
- xml2.