Postgres Compatibility
See the supported and unsupported Postgres features and extensions Vercel supports.Vercel Postgres is available on Hobby and Pro plans for customers with existing Vercel Postgres storage. You can create a new Postgres storage with the Neon Marketplace integration if you don't have an existing Vercel Postgres store. Existing Vercel Postgres storage will be automatically transitioned to the Neon Serverless Postgres product integration from the first week of December 2024, and expected to be completed by the end of January 2025. No action is required on your end and there will be no downtime and pricing change.
Vercel Postgres has integrated many PostgreSQL extensions, which will be automatically available to your database. Vercel's Postgres compatibility is based on our Neon integration.
The following table lists the PostgreSQL extensions Vercel Postgres supports.
Extension | Extension Version (PostgreSQL 15) | Note |
---|---|---|
address_standardizer | 3.3.3 | |
address_standardizer_data_us | 3.3.3 | |
autoinc (spi) | 1.0 | |
bloom | 1.0 | |
btree_gin | 1.3 | |
btree_gist | 1.7 | |
citext | 1.6 | |
cube | 1.5 | |
dict_int | 1.0 | |
earthdistance | 1.1 | |
fuzzystrmatch | 1.1 | |
h3_pg | 4.1.3 | |
hll | 2.18 | |
hstore | 1.8 | |
hypopg | 1.4.1 | |
insert_username (spi) | 1.0 | |
intagg | 1.1 | |
intarray | 1.5 | |
ip4r | 2.4.2 | |
isn | 1.2 | |
lo | 1.1 | |
ltree | 1.2 | |
moddattime (spi) | 1.0 | |
pg_graphql | 1.4.0 | |
pg_hashids | 1.2.1 | |
pg_hint_plan | 1.7.0 | |
pg_ivm | 1.9 | |
pg_jsonschema | 0.2.0 | |
pg_partman | 5.1.0 | |
pg_prewarm | 1.2 | |
pg_roaringbitmap | 0.5 | |
pg_stat_statements | 1.10 | |
pg_tiktoken | 0.0.1 | |
pg_trgm | 1.6 | |
pg_uuidv7 | 1.6.0 | |
pgcrypto | 1.3 | |
pgjwt | 0.2.0 | |
pgrouting | 3.4.2 | The PostGIS extension must be installed first. |
pgrowlocks | 1.2 | |
pgstattuple | 1.5 | |
pgTAP | 1.3.3 | |
pgvector | 0.7.4 | Install with CREATE EXTENSION vector; |
pgx_ulid | 0.1.3 | Install with CREATE EXTENSION vector; |
plcoffee | 3.1.8 | |
plls | 3.1.8 | |
plpgsql | 1.0 | Pre-installed with PostgreSQL. |
plpgsql_check | 2.5.3 | |
plv8 | 3.2.3 | |
postgis | 3.3.3 | |
postgis_raster | 3.3.3 | |
postgis_tiger_geocoder | 3.3.3 | Cannot be installed using the Vercel Postgres SQL Editor. Use your psql user credentials to install this extension. |
postgis_topology | 3.3.3 | |
prefix | 1.2.0 | |
rdkit | 4.6.0 | |
refint (spi) | 1.0 | |
roaringbitmap | 0.5 | |
rum | 1.3 | |
seg | 1.4 | |
tablefunc | 1.0 | |
tcn | 1.0 | |
timescaledb | 2.17.0 | Only Apache-2 licensed features are supported. Compression is not supported. |
tsm_system_rows | 1.0 | |
tsm_system_time | 1.0 | |
unaccent | 1.1 | |
unit | 7 | |
uuid-ossp | 1.1 | Double-quote the extension name when installing: CREATE EXTENSION "uuid-ossp" |
xml2 | 1.1 |
- Vercel Postgres supports the
uuid-ossp
extension for generating UUIDs instead of theuuid
extension. - The
sslinfo
extension is not supported. Vercel Postgres handles connections through a proxy that checks SSL. - The
pg_cron
extension is not supported. Vercel Postgres 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 external scheduler like Vercel Cron Jobs. - The
file_fdw
extension is not supported. Files would not remain accessible when Vercel Postgres scales to zero.
You can install extensions from the CLI interface in your dashboard on Vercel, or with a PostgreSQL client of your choice.
CREATE EXTENSION vector;
ALTER EXTENSION extension_name UPDATE TO 'x.x.x';
You can check the version of an extension with:
SELECT * FROM extension_name;
Was this helpful?