This release includes the first Release Candidate of PostgreSQL 17, PostGIS 3.5.0 alpha 2, pgRouting 3.6.2 and various updates to the toolset.

An overview of the changes in PostgreSQL 17 can be found in the Release Announcement and full details in the Release Notes. For changes in PostGIS 3.5, see the Release Notes in the dev documentation or the 3.5.0alpha2 news file.

Postgres.app now includes all our usual extensions for PostgreSQL 17 in their latest version.

The PostgreSQL 12-16 binaries are identical to those in the Postgres.app 2.7.6 release.

Known Issues

PostGIS does not currently ship with support for postgis-sfcgal and protobuf-backed ST_AsMVT.

With these releases, Postgres.app will be updated to the latest minor versions of PostgreSQL:

• PostgreSQL 16.4 with PostGIS 3.4.2
• PostgreSQL 15.8 with PostGIS 3.3.6
• PostgreSQL 14.13 with PostGIS 3.2.7
• PostgreSQL 13.16 with PostGIS 3.1.11
• PostgreSQL 12.20 with PostGIS 3.0.11

Please refer to the PostgreSQL Release Notes for details or the Release Announcement for a brief overview.

Upgrading pgvector

PostgreSQL 15 and higher now include pgvector version 0.7.4. If you are using pgvector, run the following query to upgrade pgvector:

ALTER EXTENSION vector UPDATE;

You have to execute this query in every database that is using pgvector.

Inclusion of pljs

As a new extension for PostgreSQL 14 and higher, we are including a preview of pljs, a potential lightweight replacement for the plv8 extension that we continue to ship with PostgreSQL 13 and below.

Upgrades to pldebugger and wal2json

This release updates pldebugger to 1.8 and, for PostgreSQL 13 and higher, wal2json to 2.6. These updates don't change the API and don't require a manual upgrade step. If you are using wal2json, please note that this update fixes some bugs and introduces new features.

This release contains the latest beta of PostgreSQL 17.

You can find all the details in the PostgreSQL Release Notes.

Postgres.app does not yet include all the usual extensions for PostgreSQL 17, especially PostGIS is still being worked on. As a new extension, we include a preview of pljs, a potential replacement for the plv8 extension that we removed in PostgreSQL 14.

The binaries of PostgreSQL 12-16 are identical to those in Postgres.app release 2.7.3.

This is the first Beta version of PostgreSQL 17.

You can find an overview of the changes in PostgreSQL 17 in the Release Announcement and all the details in the Release Notes.

Postgres.app does not yet include all the usual extensions for PostgreSQL 17, especially PostGIS is still being worked on. As a new extension, we include a preview of pljs, a potential replacement for the plv8 extension that we removed in PostgreSQL 14.

The binaries of PostgreSQL 12-16 are identical to those in Postgres.app release 2.7.3.

Known Issues

PostgreSQL crashes when running the regression tests of the contrib extension xml2. This may be a build issue with libxml2 and will be investigated further.

These releases contains the latest versions of PostgreSQL and PostGIS:

• PostgreSQL 16.3 with PostGIS 3.4.2
• PostgreSQL 15.7 with PostGIS 3.3.6
• PostgreSQL 14.12 with PostGIS 3.2.7
• PostgreSQL 13.15 with PostGIS 3.1.11
• PostgreSQL 12.19 with PostGIS 3.0.11

Please refer to the PostgreSQL Release Notes for details

Security Fixes

A security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they shouldn't. If this is of concern in your installation, follow the steps in the release notes.

Upgrading PostGIS

If you are using PostGIS, please execute the following query after upgrading Postgres.app:

SELECT postgis_extensions_upgrade();

You have to execute this query in every database that is using PostGIS

Upgrading pgvector

PostgreSQL 15 and 16 now include pgvector version 0.7.0. If you are using pgvector, run the following query to upgrade pgvector:

ALTER EXTENSION vector UPDATE;

You have to execute this query in every database that is using pgvector

Known Issues

Due to a build order issue, NetCDF was built without zstd support. We are not sure if anyone is using this feature, but if you are, please let us know in Github issues, and stick with 2.7.2 for now. We hope to resolve this for the next release.

@jakob has created a really nice UI for managing Client App Permissions in the preferences, which also allows you to change decisions later. New connection attempts are now added even if the helper application was unable to show the permission dialog, so this should provide a workaround to (#749).

Also, the 2.7.x releases had a bug where disabling "Ask for permission when apps connect without password" was not respected if the server was started automatically on login or from the menu (#752). This release fixes that.

The PostgreSQL builds are identical to 2.7.1:

• PostgreSQL 12.18 with PostGIS 3.0.10
• PostgreSQL 13.14 with PostGIS 3.1.10
• PostgreSQL 14.11 with PostGIS 3.2.6
• PostgreSQL 15.6 with PostGIS 3.3.5
• PostgreSQL 16.2 with PostGIS 3.4.1

Postgres.app shows a permission prompt when an app attempts to connect for the first time. For more information, see https://postgresapp.com/documentation/app-permissions.html

This release contains the latest bugfixes for all supported versions of PostgreSQL.

• PostgreSQL 12.18 with PostGIS 3.0.10
• PostgreSQL 13.14 with PostGIS 3.1.10
• PostgreSQL 14.11 with PostGIS 3.2.6
• PostgreSQL 15.6 with PostGIS 3.3.5
• PostgreSQL 16.2 with PostGIS 3.4.1

This release removes PostgreSQL 11. If you are still using PostgreSQL 11, please create a dump before upgrading the app.

You can find an overview of the fixes in PostgreSQL in the Release Announcement and all details in the Release Notes. In particular, there is a note about GIN-Indexes that may require a post-upgrade step.

PostgreSQL 15 and 16 include a new version of the pgvector extension. Run ALTER EXTENSION vector UPDATE; to update if you use this.

Postgres.app now shows a permission prompt when an app attempts to connect for the first time. For more information, see https://postgresapp.com/documentation/app-permissions.html

Postgres.app now shows a permission prompt when an app attempts to connect for the first time. For more information, see https://postgresapp.com/documentation/app-permissions.html

This release also contains the latest versions of PostGIS and GEOS. The following PostgreSQL versions are available:

• PostgreSQL 11.22 with PostGIS 2.5.9
• PostgreSQL 12.17 with PostGIS 3.0.10
• PostgreSQL 13.13 with PostGIS 3.1.10
• PostgreSQL 14.10 with PostGIS 3.2.6
• PostgreSQL 15.5 with PostGIS 3.3.5
• PostgreSQL 16.1 with PostGIS 3.4.1

If you are using PostGIS, remember to run SELECT postgis_extensions_upgrade(); for each PostGIS enabled database to update the extension's SQL definitions.

This release also includes a minor bug fix where the app did not activate correctly when opened from the menu item (issue #743).

The November builds with PostgreSQL 12, 13, 14 and 15 were missing the "latest" symlink (#735).

This release fixes this issue. It is otherwise identical to 2.6.8.

This release contains the latest bugfixes for all supported versions of PostgreSQL.

• PostgreSQL 16.1 with PostGIS 3.4.0
• PostgreSQL 15.5 with PostGIS 3.3.4
• PostgreSQL 14.10 with PostGIS 3.2.5
• PostgreSQL 13.13 with PostGIS 3.1.9
• PostgreSQL 12.17 with PostGIS 3.0.9
• PostgreSQL 11.22 with PostGIS 2.5.9

Notable changes since Postgres.app 2.6.7:

• PostGIS: support for writeable MVT in OGR
• PostGIS: support for netCDF in GDAL / OGR (#731) with PostgreSQL 16
• New versions of extensions pgrouting and pgvector. Run ALTER EXTENSION ... UPDATE to update
• PostgreSQL got several fixes affecting index creation and maintenance. Please check the release notes whether or not your databases may be affected and reindexing would be advisable.
• Fixed an issue where Postgres.app didn't auto-start when not in /Applications
• Fixed an issue where Postgres.app didn't launch on macOS 10.13 when not in /Applications

You can find an overview of the fixes in PostgreSQL in the Release Announcement and all details in the Release Notes.

This will likely be the final release of PostgreSQL 11. If you still have databases running on PostgreSQL 11, you should consider upgrading your database after installing this update.

The single version releases containing PostgreSQL 12, 13, 14 and 15 have been withdrawn, please refer to the fixed downloads in the 2.6.8a Release.