Supported extensions
All extensions listed below are currently available for PostgreSQL 17. These extensions provide additional functionality to enhance your database, from spatial data processing to text search and monitoring tools.
Available PostgreSQL extensions
Extension | Description | Version | Prerequisites |
---|---|---|---|
address_standardizer | Standardizes address data using rules-based parsing | 3.5.3 | |
address_standardizer_data_us | US address data for address_standardizer | 3.5.3 | |
amcheck | Functions for verifying relation integrity | 1.4 | |
auto_explain | Automatic query plan logging | 1.0 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
autoinc | Functions for automatic increment of fields | 1.0 | |
bloom | Bloom index access method | 1.0 | |
btree_gin | Support for indexing common datatypes in GIN | 1.3 | |
btree_gist | Support for indexing common datatypes in GiST | 1.7 | |
citext | Case-insensitive text data type | 1.6 | |
cube | Multi-dimensional cube data type | 1.5 | |
dblink | Cross-database queries | 1.2 | |
dict_int | Text search dictionary template for integers | 1.0 | |
dict_xsyn | Text search dictionary template for synonyms | 1.0 | |
earthdistance | Earth distance calculations | 1.2 | |
file_fdw | Foreign data wrapper for flat file access | 1.0 | |
fuzzystrmatch | Determine similarities and distance between strings | 1.2 | |
hll | HyperLogLog data type for cardinality estimation | 2.18 | |
hstore | Key-value store data type | 1.8 | |
hypopg | Hypothetical indexes for query planning | 1.4.2 | |
intagg | Integer aggregator (deprecated in favor of array_agg) | 1.1 | |
intarray | Functions for 1-D arrays of integers | 1.5 | |
insert_username | Automatic username insertion | 1.0 | |
ip4r | IPv4 and IPv6 types and functions | 2.4 | |
isn | International Standard Number data types | 1.2 | |
lo | Large Object maintenance functions | 1.1 | |
ltree | Tree-like structures data type | 1.3 | |
moddatetime | Automatic timestamp updates | 1.0 | |
pageinspect | Low-level page inspection | 1.12 | |
pg_buffercache | Buffer cache inspection | 1.5 | |
pg_cron | Job scheduler for PostgreSQL | 1.6 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pg_freespacemap | Free space map examination | 1.2 | |
pg_hint_plan | Query execution plan hinting | 1.7.0 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pg_partman | Partition management extension for PostgreSQL | 5.2.4 | |
pg_prewarm | Database prewarming | 1.2 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pg_repack | Remove bloat from tables and indexes without exclusive lock | 1.5.2 | |
pg_surgery | Row surgery functions for modifying rows | 1.0 | |
pg_trgm | Trigram matching for similarity searches | 1.6 | |
pg_visibility | Visibility map examination | 1.2 | |
pg_walinspect | WAL inspection functions | 1.1 | |
pgrowlocks | Row locking information | 1.2 | |
pg_stat_statements | Query execution statistics | 1.11 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pg_stattuple | Functions to show tuple-level statistics | 1.5 | |
pgaudit | Audit logging extension for PostgreSQL | 17.1 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pgcrypto | Cryptographic functions | 1.3 | |
pgrouting | Routing functionality for PostGIS/PostgreSQL | 3.8.0 | |
pglogical | Logical replication extension for PostgreSQL | 2.4.5 | This extension must be enabled by Xata support. Please open a support ticket with your branch id for the request. |
pgtap | Unit testing framework for PostgreSQL | 1.3.3 | |
plpgsql | PL/pgSQL procedural language | 1.0 | |
postgres_fdw | Foreign data wrapper for PostgreSQL | 1.1 | |
postgis | PostGIS geometry and geography spatial types and functions | 3.5.3 | |
postgis_raster | PostGIS raster extension | 3.5.3 | |
postgis_sfcgal | PostGIS SFCGAL support | 3.5.3 | |
postgis_tiger_geocoder | PostGIS tiger geocoder and reverse geocoder | 3.5.3 | |
postgis_topology | PostGIS topology spatial types and functions | 3.5.3 | |
prefix | Prefix matching operator | 1.2.0 | |
refint | Referential integrity triggers (example) | 1.0 | |
seg | Floating-point intervals | 1.4 | |
sslinfo | Information about SSL connections | 1.2 | |
tablefunc | Functions that manipulate whole tables, including crosstab | 1.0 | |
tcn | Triggered change notifications | 1.0 | |
tsm_system_rows | TABLESAMPLE method which accepts number of rows | 1.0 | |
tsm_system_time | TABLESAMPLE method which accepts time in milliseconds | 1.0 | |
unaccent | Text search dictionary that removes accents | 1.1 | |
uuid-ossp | UUID generation functions | 1.1 | |
vector | Vector similarity search for PostgreSQL | 0.8.0 | |
wal2json | Logical replication output plugin for JSON | 2.6 | |
xml2 | XPath querying and XSLT support | 1.1 |
Request an extension
Need an extension we don't have? 📩 Request an extension
We're always looking to expand our extension offerings. If you need an extension that's not currently available, please let us know through our feature request portal. We'll review your request and respond there.
Getting help
If you need help with a specific extension, we recommend checking the official documentation linked in the table above. For general PostgreSQL extension support, you can also refer to the PostgreSQL documentation.
If you run into an issue or discover a bug with an extension, we recommend reporting it to the extension's upstream maintainers. If a fix is released, we're happy to update to the latest version of the extension.
For additional support, you can also contact our support team.
Custom extensions
We don't actively maintain third-party extension code, but we're happy to help you get the extensions you need. If you require a custom extension that's not listed above, we encourage you to contact our support team to discuss.
BYOC for custom extensions
If you need to install custom extensions that aren't available in our standard offering, consider our Bring Your Own Cloud (BYOC) deployment model. This allows you to run the entire Xata dataplane in your own Kubernetes cluster, giving you full control over which extensions are installed and configured.