This is a pre-release build for testing.

• GUI improvements from issue #842
• another build of Postgres 19 beta 3, but with a newer PostGIS (3.7.0rc1)

We offer two builds with the following PostgreSQL versions:

• PostgreSQL 14.24 with PostGIS 3.2.10
• PostgreSQL 15.19 with PostGIS 3.3.10
• PostgreSQL 16.15 with PostGIS 3.4.6
• PostgreSQL 17.11 with PostGIS 3.5.6
• PostgreSQL 18.6 with PostGIS 3.6.3
• PostgreSQL 19beta3 with PostGIS 3.7.0rc1

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

Included PostgreSQL and PostGIS versions

• PostgreSQL 18.6 with PostGIS 3.6.3
• PostgreSQL 17.11 with PostGIS 3.5.6
• PostgreSQL 16.15 with PostGIS 3.4.6
• PostgreSQL 15.19 with PostGIS 3.3.10
• PostgreSQL 14.24 with PostGIS 3.2.10

You can find an overview of the PostgreSQL fixes and recommended post-update steps in the Release Announcement, and all the details in the Release Notes. Specifically, if you are using a third-party logical decoding output plugin such as the bundled wal2json, you need to set the new GUC output_plugin_libraries to allow it to load. Furthermore, indexes using the extension modules btree_gist and ltree may require a post-upgrade step as well as parallel bullt GIN indexes in PostgreSQL 18.

What else is new?

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

Updates to the beta version of PostgreSQL 19 are published in the release announcement of release 3alpha8.

This is the third Beta version of PostgreSQL 19, the second Beta version of PostGIS 3.7 and an updated 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.

Extensions

This release updates pgvector to 0.8.6 and PostGIS to 3.7.0beta2, as well as some of their dependencies.

Please note that the address_standardizer and postgis_tiger_geocoder extensions have been removed from PostGIS. These, along with other extensions that were previously bundled with Postgres.app, will be made available as separate downloads for PostgreSQL 19 in the Postgres.app Extensions repository. The GDAL update retires several older, unmaintained raster and vector (OGR) drivers, while adding support for others by default. Due to various dependencies, not all format drivers are included in Postgres.app. If you require a format that is not currently included, please open an issue.

What else is new?

• Settings and About are available from the side-bar
• Servers can again be removed from the side-bar using the context menu

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. When upgrading from 19beta1 or 19beta2 to 19beta3, you will need to dump and restore your database.

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

This is the second Beta version of PostgreSQL 19, the first Alpha version of PostGIS 3.7 and an updated 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.

Extensions

This release includes pgvector 0.8.5, PostGIS 3.7.0alpha1, and upgraded dependencies, including the latest major versions of GDAL, GEOS, SFCGAL, and Proj. Please note that the address_standardizer and postgis_tiger_geocoder extensions have been removed from PostGIS. These, along with other extensions that were previously bundled with Postgres.app, will be made available as separate downloads for PostgreSQL 19 in the Postgres.app Extensions repository. The GDAL update retires several older, unmaintained raster and vector (OGR) drivers, while adding support for others by default. Due to various dependencies, not all format drivers are included in Postgres.app. If you require a format that is not currently included, please open an issue.

What else is new?

• The way in which Postgres.app enables 'Start at Login' has been changed again. (see #844 for discussion)
• Ensure that the settings window for Postgres.app reflects the 'Start at login' state if this is changed in the system settings.
• The behaviour of showing/hiding the application window has been changed.
• Internal modernisations.

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. When upgrading from 19beta1 to 19beta2, you will need to dump and restore your database.

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

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.