Postgres extensions
Neon supports the Postgres extensions shown in the following table. The supported version of the extension sometimes differs by Postgres version.
Extension | PG14 | PG15 | PG16 | Notes |
---|---|---|---|---|
address_standardizer | 3.3.3 | 3.3.3 | 3.3.3 | |
address_standardizer_data_us | 3.3.3 | 3.3.3 | 3.3.3 | |
autoinc (spi) | 1.0 | 1.0 | 1.0 | |
bloom | 1.0 | 1.0 | 1.0 | |
btree_gin | 1.3 | 1.3 | 1.3 | |
btree_gist | 1.6 | 1.7 | 1.7 | |
citext | 1.6 | 1.6 | 1.6 | |
cube | 1.5 | 1.5 | 1.5 | |
dict_int | 1.0 | 1.0 | 1.0 | |
earthdistance | 1.1 | 1.1 | 1.1 | |
fuzzystrmatch | 1.1 | 1.1 | 1.1 | |
h3 | 4.1.3 | 4.1.3 | 4.1.3 | Some components have been split out into the h3_postgis extension. Install both the h3 and h3_postgis extensions. |
h3_postgis | 4.1.2 | 4.1.3 | 4.1.2 | Install with CREATE EXTENSION h3_postgis CASCADE; (requires postgis and postgis_raster ) |
hll | 2.18 | 2.18 | 2.18 | |
hstore | 1.8 | 1.8 | 1.8 | |
hypopg | 1.4.0 | 1.4.0 | 1.4.0 | |
insert_username (spi) | 1.0 | 1.0 | 1.0 | |
intagg | 1.1 | 1.1 | 1.1 | |
intarray | 1.5 | 1.5 | 1.5 | |
ip4r | 2.4.2 | 2.4.2 | 2.4.2 | |
isn | 1.2 | 1.2 | 1.2 | |
lo | 1.1 | 1.1 | 1.1 | |
ltree | 1.2 | 1.2 | 1.2 | |
moddattime (spi) | 1.0 | 1.0 | 1.0 | |
neon_utils | 1.0 | 1.0 | 1.0 | |
pg_graphql | 1.4.0 | 1.4.0 | 1.4.0 | |
pg_hashids | 1.2.1 | 1.2.1 | 1.2.1 | |
pg_hint_plan | 1.4.1 | 1.5.0 | 1.6.0 | |
pg_jsonschema | 0.2.0 | 0.2.0 | 0.2.0 | |
pg_prewarm | 1.2 | 1.2 | 1.2 | |
pg_roaringbitmap | 0.5 | 0.5 | 0.5 | |
pg_stat_statements | 1.10 | 1.10 | 1.10 | |
pg_tiktoken | 0.0.1 | 0.0.1 | 0.0.1 | |
pg_trgm | 1.6 | 1.6 | 1.6 | |
pg_uuidv7 | 1.0 | 1.0 | 1.0 | |
pgcrypto | 1.3 | 1.3 | 1.3 | |
pgjwt | 0.2.0 | 0.2.0 | 0.2.0 | |
pgrouting | 3.4.2 | 3.4.2 | 3.4.2 | The PostGIS extension must be installed first. |
pgrowlocks | 1.2 | 1.2 | 1.2 | |
pgstattuple | 1.5 | 1.5 | 1.5 | |
pgtap | 1.2.0 | 1.2.0 | 1.2.0 | |
pgvector | 0.5.0 | 0.5.0 | 0.5.0 | Install with CREATE EXTENSION vector; |
pgx_ulid | 0.1.3 | 0.1.3 | 0.1.3 | Install with CREATE EXTENSION ulid; |
plcoffee | 3.1.5 | 3.1.5 | 3.1.8 | |
plls | 3.1.5 | 3.1.5 | 3.1.8 | |
plpgsql | 1.0 | 1.0 | 1.0 | Pre-installed with Postgres. |
plpgsql_check | 2.5.3 | 2.5.3 | 2.5.3 | |
plv8 | 3.1.5 | 3.1.5 | 3.1.8 | |
postgis | 3.3.3 | 3.3.3 | 3.3.3 | |
postgis_raster | 3.3.3 | 3.3.3 | 3.3.3 | |
postgis_sfcgal | 3.3.3 | 3.3.3 | 3.3.3 | |
postgis_tiger_geocoder | 3.3.3 | 3.3.3 | 3.3.3 | Cannot be installed using the Neon SQL Editor. Use your psql user credentials to install this extension. |
postgis_topology | 3.3.3 | 3.3.3 | 3.3.3 | |
prefix | 1.2.0 | 1.2.0 | 1.2.0 | |
rdkit | 4.3.0 | 4.3.0 | 4.3.0 | |
refint (spi) | 1.0 | 1.0 | 1.0 | |
roaringbitmap | 0.5 | 0.5 | 0.5 | |
rum | 1.3 | 1.3 | 1.3 | |
seg | 1.4 | 1.4 | 1.4 | |
tablefunc | 1.0 | 1.0 | 1.0 | |
tcn | 1.0 | 1.0 | 1.0 | |
timescaledb | 2.10.1 | 2.10.1 | 2.13.0 | Only Apache-2 licensed features are supported. Compression is not supported. |
tsm_system_rows | 1.0 | 1.0 | 1.0 | |
tsm_system_time | 1.0 | 1.0 | 1.0 | |
unaccent | 1.1 | 1.1 | 1.1 | |
unit | 7 | 7 | 7 | |
uuid-ossp | 1.1 | 1.1 | 1.1 | Double-quote the extension name when installing: CREATE EXTENSION "uuid-ossp" |
xml2 | 1.1 | 1.1 | 1.1 |
Install an extension
Unless otherwise noted, supported extensions can be installed using CREATE EXTENSION syntax.
You can install extensions from the Neon SQL Editor or from a client such as psql
that permits running SQL queries. For information about using the Neon SQL Editor, see Query with Neon's SQL Editor. For information about using the psql
client with Neon, see Connect with psql.
Update an extension version
Neon updates supported extensions as new versions become available. Version updates are communicated in the Release notes. To check the current version of extensions you have installed, query the pg_extension
table:
You can update an extension to the latest version using ALTER EXTENSION <extension_name> UPDATE TO <new_version>
syntax. For example:
Extension support notes
- Neon supports the
uuid-ossp
extension for generating UUIDs instead of theuuid
extension. - The
sslinfo
extension is not supported. Neon handles connections via a proxy that checks SSL. - The
pg_cron
extension is not supported. Neon scales to zero when it is not being used, which means that a scheduler that runs inside the database cannot be implemented. Consider using an scheduler that runs externally instead. - The
file_fdw
extension is not supported. Files would not remain accessible when Neon scales to zero.
Request extension support
To request support for a Postgres extension, please post your request to the Neon community forum. Neon Pro Plan users can open a support ticket from the console. For more detail, see Getting Support.
Custom-built extensions
Neon supports custom-built Postgres extensions for exclusive use with your Neon account. If you developed your own Postgres extension and want to use it with Neon, please post your request to the Neon community forum. Neon Pro Plan users can open a support ticket from the console. For more detail, see Getting Support. Please include the following information in your request:
- A repository link or archive file containing the source code for your extension
- A description of what the extension does, instructions for compiling it, and any prerequisites
- Whether an NDA or licensing agreement is necessary for Neon to provide support for your extension
Please keep in mind that certain restrictions may apply with respect to Postgres privileges and local file system access. Neon features such as Autoscaling and Auto-suspend may limit the types of extensions we can support.
Depending on the nature of your extension, Neon may also request a liability waiver.
Need help?
Join the Neon community forum to ask questions or see what others are doing with Neon. Neon Pro Plan users can open a support ticket from the console. For more detail, see Getting Support.
Last updated on