This fixes a memory leak that caused UI lag after showing / hiding the app.

Includes the following PostgreSQL versions (same as 3alpha4 and 3alpha5):

• PostgreSQL 14.23 with PostGIS 3.2.10
• PostgreSQL 15.18 with PostGIS 3.3.10
• PostgreSQL 16.14 with PostGIS 3.4.6
• PostgreSQL 17.10 with PostGIS 3.5.6
• PostgreSQL 18.4 with PostGIS 3.6.3
• PostgreSQL 19beta1 without PostGIS

Known Issue:

Closing the main window should hide the app. Sometimes this works, sometimes it doesn't and the menu bar + dock icon stay visible until you switch to another app.

Working on Postgres.app 3.0

• changed how Postgres.app enables "start at login"
• fixes an issue where app was not activated after checking for updates on macos 27 Beta
• preferences show instructions when background activities are disabled in system settings

The binaries included with this release are the same as those in the 3alpha4.

This is the first Beta version of PostgreSQL 19 and a preview towards Postgres.app 3.0.

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

Postgres.app does not yet include the bundled extensions for PostgreSQL 19.

What else is new?

• Removed Postgres.app's helper apps (#844). LoginHelper remains as a stub for a smooth transition.
• Reworked the start-at-login behavior, which can again be controlled in the Settings window.
• Postgres.app now moves to the background when its last window is closed. Quitting shows a prompt offering to keep it running in the background instead.
• Servers now stop automatically when you quit Postgres.app or log out (#834).
• Fewer warnings on macOS Tahoe (#817).
• System requirements: the minimum supported OS is now macOS 11.

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.

The binaries of PostgreSQL 14-18 are identical to those in Postgres.app release 2.9.5.

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

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.4 with PostGIS 3.6.3
• PostgreSQL 17.10 with PostGIS 3.5.6
• PostgreSQL 16.14 with PostGIS 3.4.6
• PostgreSQL 15.18 with PostGIS 3.3.10
• PostgreSQL 14.23 with PostGIS 3.2.10

You can find an overview of the PostgreSQL fixes in the Release Announcement, and all the details in the Release Notes. In particular, for PostgreSQL 18 there is a note about DEFERRABLE foreign-key constraints whose ENFORCED status has been altered, that may require a post-upgrade step.

What else is new?

• The pgvector extension has been updated to 0.8.2. If you use it, make sure you run the command ALTER EXTENSION vector UPDATE; in any databases using pgvector.
• Several dependencies got minor updates.

Upgrading PostGIS

The version of PostGIS has been updated to 3.2.10, 3.3.10, 3.4.6, 3.5.6 and 3.6.3 respectively. 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 PostgreSQL 18: If you are using postgis_topology, have topogeometry columns, and you are upgrading from a version earlier than PostGIS 3.6.1 (Postgres.app v2.9.2), make sure you run the following function after upgrading to fix any topogeometry corruption:

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

The PostgreSQL project has announced an out-of-cycle bug fix release due to regressions in the Feb 12 releases.

If you are updating from Postgres.app 2.9.2 or earlier, please also see the Postgres.app 2.9.3 release notes.

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.3 with PostGIS 3.6.2
• PostgreSQL 17.9 with PostGIS 3.5.5
• PostgreSQL 16.13 with PostGIS 3.4.5
• PostgreSQL 15.17 with PostGIS 3.3.9
• PostgreSQL 14.22 with PostGIS 3.2.9

You can find an overview of the PostgreSQL fixes in the Release Announcement, and all the details in the Release Notes. In particular, for PostgreSQL 18 there is a note about the volatility marking of the json_strip_nulls() and jsonb_strip_nulls() functions that can be corrected in existing databases by a catalog update.

Upgrading PostGIS

The version of PostGIS included with PostgreSQL 14-15 has been updated to 3.2.9 and 3.3.9 including patches for the postgis_tiger_geocoder upgrade issue. If you use PostGIS in these versions, please run the following query after upgrading Postgres.app to update the extensions in any databases using PostGIS: SELECT postgis_extensions_upgrade();

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

Note: The PostgreSQL project has announced that these releases contain regressions in the substring() function on multi-byte text values and with WAL replay on a standby server. If you are depending on these features, please wait for the fixed releases scheduled for next week and stick with v2.9.2 until then.

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.2 with PostGIS 3.6.2
• PostgreSQL 17.8 with PostGIS 3.5.5
• PostgreSQL 16.12 with PostGIS 3.4.5
• PostgreSQL 15.16 with PostGIS 3.3.8
• PostgreSQL 14.21 with PostGIS 3.2.8

You can find an overview of the PostgreSQL fixes in the Release Announcement, and all the details in the Release Notes. In particular, for PostgreSQL 18 there is a note about indexes on ltree columns that may require a reindex post-upgrade.

What else is new?

• A potential crash in the Permission Dialog has been fixed that could occur if the client application that is trying to connect was running translocated.
• The pljs extension has been updated to 1.0.5. If you use it, make sure you run the command ALTER EXTENSION pljs UPDATE;.
• Several dependencies got minor updates.

Upgrading PostGIS

The version of PostGIS included with PostgreSQL 16-18 has been updated to 3.4.5, 3.5.5 and 3.6.2 respectively. If you use PostGIS in these versions, please run the following query after upgrading Postgres.app to update the extensions in any databases using PostGIS: SELECT postgis_extensions_upgrade();

For PostgreSQL 18: If you are using postgis_topology and have topogeometry columns, and you are upgrading from a version earlier than PostGIS 3.6.1, make sure you run the following function after upgrading to fix any topogeometry corruption:

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

The PostGIS updates for PostgreSQL 14 and 15 will be delivered with the next release, after a bug with upgrades has been fixed.

PostgreSQL 13 EOL

This release removes PostgreSQL 13 as it is no longer supported. If you are still using PostgreSQL 13, please create a dump before upgrading.

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.