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;