This release updates PostGIS for PostgreSQL 18 to fix a data corruption bug with topologies. In addition, a possible crash in the xml2 contrib extension should be fixed. The PostgreSQL 13–17 binaries are identical to those in the 2.9.1 Postgres.app release. For more information and downloads, please refer to that release.

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.1 with PostGIS 3.6.1
• PostgreSQL 17.7 with PostGIS 3.5.4
• PostgreSQL 16.12 with PostGIS 3.4.4
• PostgreSQL 15.15 with PostGIS 3.3.8
• PostgreSQL 14.20 with PostGIS 3.2.8
• PostgreSQL 13.23 with PostGIS 3.1.12

PostGIS

The version of PostGIS included with PostgreSQL 18 has been updated to 3.6.1. If you use PostGIS, please run the following query after upgrading Postgres.app to update the extensions in any databases using PostGIS: SELECT postgis_extensions_upgrade();

This fixes the bug in the postgis_topology extension that was corrupting existing topology data, among other fixes. If you use this extension and have topogeometry columns, run the following function after upgrading to fix any topogeometry corruption:

SELECT topology.FixCorruptTopoGeometryColumn(schema_name, table_name, feature_column)
FROM topology.layer;

This release includes the latest quarterly bug and security fixes for PostgreSQL, as well as other updates.

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.1 with PostGIS 3.6.0
• PostgreSQL 17.7 with PostGIS 3.5.4
• PostgreSQL 16.12 with PostGIS 3.4.4
• PostgreSQL 15.15 with PostGIS 3.3.8
• PostgreSQL 14.20 with PostGIS 3.2.8
• PostgreSQL 13.23 with PostGIS 3.1.12

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

What else is new?

• A possible crash in the auth_permission_dialog extension has been fixed and users should now get a proper error message in the rare cases where the Permission Dialog can not be displayed.
• A possible crash of the GUI when connecting to servers while the Preferences window is open was resolved (#829)
• The pljs extension, which is bundled with PostgreSQL 14 and later, has been updated to 1.0.3. If you use it, make sure you run the command ALTER EXTENSION pljs UPDATE;.
• The vector extension, which is bundled with PostgreSQL 15 and later, has been updated to 8.0.1. If you use it, make sure you run the command ALTER EXTENSION vector UPDATE;.

PostGIS

The version of PostGIS included with PostgreSQL 17 has been updated. If you use PostGIS, please run the following query after upgrading Postgres.app to update the extensions in any databases using PostGIS: SELECT postgis_extensions_upgrade();

Please be aware that PostGIS 3.6.0, which is included with PostgreSQL 18, contains a bug in the postgis_topology extension that may corrupt existing topology data. This has been fixed with PostGIS 3.6.1 included in the v2.9.2 release of Postgres.app

PostgreSQL 13 EOL

If you are still using PostgreSQL 13, please upgrade soon. This will likely be the final update for PostgreSQL 13 before it reaches the end of its support period.

This release features the all new PostgreSQL 18 and PostGIS 3.6.0.

Easier Extension Installation

Postgres.app has always shipped with a number of popular extensions, but starting with PostgreSQL 18 it is now easier than ever to install custom extensions. You can either build them yourself, or install a number of precompiled extensions available as a separate download. See https://postgresapp.com/extensions/ for more information.

Release Announcement

For a full list of changes, please refer to the PostgreSQL Release Announcement and the PostgreSQL Release Notes.

For PostgreSQL 18, this release also includes PostGIS to 3.6.0 and upgrades to many of its dependencies, notably Boost, CGAL, SFCGAL, Proj, GEOS and Protobuf. pgRouting has been updated to version 3.8.

It later emerged that PostGIS 3.6.0, which is included with PostgreSQL 18, contains a bug in the postgis_topology extension that can corrupt existing topology data.

What else is new

• If possible, the GUI crash reporter now also searches for diagnostic reports stored outside the user's home directory. Files not containing crashlogs are excluded.
• A fix has been implemented in the Permission Dialog that should resolve the Postgres.app failed to verify "trust" authentication errors that some users experienced.
• A possible crash of the GUI when connecting to servers while the Preferences window is open was resolved (#829)
• The pljs extension, which is bundled with PostgreSQL 14 and later, has been updated to 1.0.3. If you use it, make sure you run the command ALTER EXTENSION pljs UPDATE;.
• The vector extension, which is bundled with PostgreSQL 15 and later, has been updated to 8.0.1. If you use it, make sure you run the command ALTER EXTENSION vector UPDATE;.

This release features the first Release Candidate of PostgreSQL 18 and PostGIS 3.6.0.

For a full list of changes, please refer to the PostgreSQL Release Announcement and the PostgreSQL Release Notes.

This release also updates PostGIS to 3.6.0 and continues the upgrades of its dependencies to their latest major versions, notably GEOS. pljs has also received some bugfixes.

What else is new

• If possible, the GUI crash reporter now also searches for diagnostic reports stored outside the user's home directory.
• A fix has been implemented in the Permission Dialog that should resolve the Postgres.app failed to verify "trust" authentication errors that some users experienced.

Beta notice

Please note that beta versions are intended for evaluation purposes only. You may encounter bugs of varying severity. During the beta testing period, the on-disk data format of PostgreSQL is not yet stable. This means that the data directory may not be compatible with future versions. You will need to dump and restore your database when upgrading from 18beta1 to 18rc1. (18beta2 and 18beta3 are compatible).

A similar caveat applies to additional extensions installed like those released in the Postgres.app Extensions repository. During the beta period, these extensions may need to be rebuilt due to changes in the internal API. Extensions built for 18beta1 are not compatible with 18rc1.

The binaries of PostgreSQL 13-17 are identical to those in Postgres.app release 2.8.5.

This release contains the latest beta 3 of PostgreSQL 18 and beta 1 of PostGIS 3.6.0.

For a full list of changes, please refer to the PostgreSQL Release Announcement and the PostgreSQL Release Notes.

This release updates PostGIS 3.6.0 to Beta 1 and upgrades some of its dependencies to the latest major versions. pgRouting has been updated to version 3.8, and pgvector now includes the necessary patches to run on PostgreSQL 18.

Please note that beta versions are intended for evaluation purposes only. You may encounter bugs of varying severity. During the beta testing period, the on-disk data format of PostgreSQL is not yet stable. This means that the data directory may not be compatible with future versions. You will need to dump and restore your database when upgrading from 18beta1 to 18beta3. (18beta2 and 18beta3 are compatible).

A similar caveat applies to additional extensions installed like those released in the Postgres.app Extensions repository. During the beta period, these extensions may need to be rebuilt due to changes in the internal API. Extensions built for 18beta1 are not compatible with 18beta3.

The binaries of PostgreSQL 13-17 are identical to those in Postgres.app release 2.8.5.

This release includes the latest quarterly bug and security fixes for PostgreSQL, as well as other updates.

Included PostgreSQL and PostGIS versions

• PostgreSQL 17.6 with PostGIS 3.5.3
• PostgreSQL 16.10 with PostGIS 3.4.4
• PostgreSQL 15.14 with PostGIS 3.3.8
• PostgreSQL 14.19 with PostGIS 3.2.8
• PostgreSQL 13.22 with PostGIS 3.1.12

You can find an overview of the PostgreSQL fixes in the Release Announcement, and all the details in the Release Notes. As before, there are rare cases that may require reindexing of BRIN indexes.

What else is new?

• A semi-automatic crash reporter has been added, which checks for crash reports when the application starts up and offers to send them to the developers for analysis.
• OpenSSL has been updated to supported LTS releases. For PostgreSQL 13 and 14, this means that support for certain legacy digest algorithms and ciphers, which could previously be accessed via the pgcrypto extension, has been removed (see #804). There shouldn't be any impact for PostgreSQL 15 - 17.
• The pljs extension, which is bundled with PostgreSQL 14 and later, has reached its 1.0 milestone and has been updated. If you use it, make sure you run the command ALTER EXTENSION pljs UPDATE;.
• Several bugs, including a crash on macOS 12 and earlier (#822), have been resolved.

Upgrading PostGIS

The version of PostGIS included with PostgreSQL 17 has been updated. If you use PostGIS, please run the following query after upgrading Postgres.app to update the extensions in any databases using PostGIS: SELECT postgis_extensions_upgrade();

For downloads including PostgreSQL 18 Beta 3, please see Postgres.app 2.9beta.

This release contains the latest beta 2 of PostgreSQL 18 and alpha 1 of PostGIS 3.6.0.

For a full list of changes, please refer ro the PostgreSQL Release Announcement and the PostgreSQL Release Notes.

While Postgres.app does not yet include all the extensions for PostgreSQL 18 that we usually bundle, this release especially adds updated versions of PostGIS and pljs. The extensions pgvector and pldebugger are not yet compatible. Additional extensions will be released in the Postgres.app Extensions repository.

Please note that beta versions are intended for evaluation purposes only. You may encounter bugs of varying severity. During the beta testing period, the on-disk data format of PostgreSQL is not yet stable. This means that the data directory may not be compatible with future versions. You will need to dump and restore your database before upgrading from an older beta version.

The binaries of PostgreSQL 13-17 are identical to those in Postgres.app release 2.8.2.

This release fixes a bug in the extension search path code. PostgreSQL 18 Beta 1 changed the way the setting works compared to development versions.

• adds support for installing additional extensions
• adds semi-automatic crash reporter:
  Checks for crash reports on startup and offers to send them to the developers for analysis.

For testing purposes, I have added two extensions to this release:

• pgsql-http: Adds support for performing HTTP requests directly from PostgreSQL
• plv8: Use JavaScript as a procedural language in functions and stored procedures

These extensions are available as standard macOS installer packages. Double click them, then go through the steps to install them. After installing them, please restart the PostgreSQL server and activate them as usual with CREATE EXTENSION http or CREATE EXTENSION plv8

It's time for the quarterly bugfix releases. But wait! There is more!

Today we are very excited to announce the immediate availability of PostgreSQL 18beta1!

PostgreSQL 18 makes it a lot easier to distribute extensions. So for the first time, we will distribute not just Postgres.app with some popular extensions, but also provide even more extensions as separate downloads. But not today, though. Today there is only PostgreSQL 18beta1. Extensions are coming soon!

These are the new versions of PostgreSQL that are available today:

• PostgreSQL 13.21 with PostGIS 3.1.12
• PostgreSQL 14.18 with PostGIS 3.2.8
• PostgreSQL 15.13 with PostGIS 3.3.8
• PostgreSQL 16.9 with PostGIS 3.4.4
• PostgreSQL 17.5 with PostGIS 3.5.2

Update: We have removed the 18beta1 asset from this release, since it is a beta version. Brew Cask was delivering it automatically to users. We will try to make separate releases for stable updates / beta versions on Github in the future to prevent this issue.

This is a preview release for testing the new extension search path, built on the PostgreSQL master branch (version 18devel-b3219c69fc1e161df8d380c464b3f2cce3b6cab9)

It contains the following major improvements:

• extension_control_path: You can now build and load extensions outside of the app. This makes it much easier to build custom extensions, and also allows installing extensions from 3rd party sources in the future. #810
• stable Python API: you can now use PL/Python 3 with any compatible Python version from python.org #796

For testing purposes, this release also contains an extension (PL/v8) that can be installed separately.