Fly Managed Postgres now includes a built-in Extensions page in the dashboard, so you can toggle PG extensions on or off with a click. No weird commands to run—just flip the switch!
You’ll be prompted to pick or create a schema to install the extension in. In most cases public or extensions are fine options, but you can achieve namespace scoping by installing extensions into their own schemas, then using functions fully-qualified:
SELECT citext.citext_ne('Hello', 'World');
Right now you can enable trusted extensions that come bundled with Postgres 16 and the popular third-party extensions pgvector and PostGIS—previously you could only enable those two when creating a cluster, but now you can enable them on existing clusters. PostGIS unlocks related geo-extensions like postgis_raster and postgis_topology.
We’ll keep adding more extensions to that list as we learn what users need. Let us know what extensions you’d like to see supported!
Oh, you’ll also find that support for enabling (trusted) extensions with SQL statements has returned. Now you can run CREATE EXTENSION with any user that has the schema_admin role. This might be especially useful for frameworks and libraries that automatically run SQL to install required extensions and schemas.
This is not revolutionary, but it’s table stakes in a fully-managed Postgres experience and we hope it unlocks some new use-cases for you!
More details in the docs here: Supported Postgres Extensions · Fly Docs
Clusters created before July 23, 2025 will need to be upgraded to the new role system to use the Extensions management UI
