diff --git a/postgres/extensions.mdx b/postgres/extensions.mdx index 87e5f3a859..497e5f27f9 100644 --- a/postgres/extensions.mdx +++ b/postgres/extensions.mdx @@ -1,6 +1,6 @@ --- title: Supported Postgres Extensions -description: "Fly.io Managed Postgres runs Postgres 16 and 17. Enable extensions per database, including pgvector and PostGIS, and check which extensions your cluster offers." +description: "Fly.io Managed Postgres runs Postgres 16, 17 and 18. Enable extensions per database, including pgvector and PostGIS, and check which ones your cluster offers." source_url: https://fly.io/docs/mpg/extensions/ --- @@ -8,7 +8,7 @@ source_url: https://fly.io/docs/mpg/extensions/ ## Overview -Fly.io Managed Postgres (MPG) supports Postgres 16 and 17. Clusters include extensions for the Postgres version they run, including commonly used tools and utilities like `pgcrypto`, `pg_stat_monitor`, and `citext`. The PostgreSQL Extensions page allows you to enable or disable PostgreSQL extensions for your managed database cluster. Extensions add features to your database, such as new data types and functions. +Fly.io Managed Postgres (MPG) supports Postgres 16, 17 and 18. Postgres 18 is available on v2 clusters only (marked **v2** next to the cluster name). Clusters include extensions for the Postgres version they run, including commonly used tools and utilities like `pgcrypto`, `pg_stat_monitor`, and `citext`. The PostgreSQL Extensions page allows you to enable or disable PostgreSQL extensions for your managed database cluster. Extensions add features to your database, such as new data types and functions. By default the `plpgsql`, `pg_stat_monitor`, and `pgaudit` extensions are enabled and cannot be disabled. diff --git a/postgres/import.mdx b/postgres/import.mdx index f2b50ab65a..6e353b0fe1 100644 --- a/postgres/import.mdx +++ b/postgres/import.mdx @@ -27,7 +27,7 @@ Your MPG cluster runs within your Fly.io private network, so it isn't reachable Make sure `pg_dump` finishes without an error before you go on. A dump that failed partway leaves an incomplete file, and an incomplete file can restore without complaint. -3. If your `pg_dump` is version 17 or later and your cluster runs Postgres 16 (the `fly mpg create` default), remove one setting from the top of the dump. `pg_dump` 17 and later writes `SET transaction_timeout = 0;` there, and Postgres 16 doesn't know that setting. Check your version with `pg_dump --version`, then remove the line: +3. If your `pg_dump` is version 17 or later and your cluster runs Postgres 16, remove one setting from the top of the dump. `pg_dump` 17 and later writes `SET transaction_timeout = 0;` there, and Postgres 16 doesn't know that setting. Check your version with `pg_dump --version`, then remove the line: ```bash sed '1,20{/^SET transaction_timeout = 0;$/d;}' dump.sql > dump-pg16.sql ``` diff --git a/postgres/index.mdx b/postgres/index.mdx index c1f2e68df6..0ff9bd1f84 100644 --- a/postgres/index.mdx +++ b/postgres/index.mdx @@ -31,7 +31,7 @@ You'll be able to access: ### Current limitations {#whats-not-there-yet} -- **Major version upgrades:** You choose Postgres 16 or 17 when you create a cluster, and you can't upgrade a cluster in place. To move to a newer major version, create a new cluster and copy your data with `pg_dump` and psql. See [Import data](/postgres/import). +- **Major version upgrades:** You choose Postgres 16, 17 or 18 when you create a cluster, and you can't upgrade a cluster in place. Postgres 18 is available on v2 clusters only. To move to a newer major version, create a new cluster and copy your data with `pg_dump` and psql. See [Import data](/postgres/import). - **Minor versions and security patches:** New Postgres images include the latest minor release. We roll out new images during your cluster's [maintenance window](/postgres/maintenance-windows). v1 clusters, which have no **v2** badge next to the cluster name in the dashboard, don't get new images. PgBouncer, PostGIS and pg_repack versions are pinned and change only when we update them. - **Third-party extensions:** `pgvector` and `PostGIS` are supported, and `pg_repack` on v2 clusters, along with the bundled Postgres extensions marked as available on the [Extensions page](/postgres/extensions). To request another extension, [contact support](/about/support). - **Alerting:** We email your organization when maintenance starts and finishes, but there are no alerts for metrics like CPU or storage. Use [metrics](/postgres/metrics) to watch your cluster.