PostgreSQL 15 and PostGIS 3.3

Waan

Whenever ArcGIS Pro 3.2 is released, will it be certified to work with PostgreSQL 15 and/or PostGIS 3.3? I'd love to use some of the new/improved PostGIS 3.3 functions alongside our SDE data.

Prior discussion indicates that PostgreSQL version compatibility typically goes up a version with each new major release of ArcGIS Pro ... and I've also seen hints that ArcGIS Pro 3.2 will be released later in 2023 or in Q1 of calendar-year 2024.

MMBR

PostgreSQL 15 / PostGIS 3.3.3 is expected to be certified and supported with the Pro 3.2 / ArcGIS Enterprise 11.2 release.

ArcGIS 11.1 and ArcGIS Pro 3.1 requirements for PostgreSQL

The following versions of PostgreSQL and PostGIS are supported with ArcGIS. The specific versions listed are the minimum minor version supported and certified for each supported major release of PostgreSQL and PostGIS. Newer minor versions are supported, but are not certified unless otherwise stated. The PostgreSQL version and updates must also be supported by the PostgreSQL Global Development Group.

• PostgreSQL 14.5 (64 bit)
  • PostGIS 3.2
• PostgreSQL 13.6 (64 bit)
  • PostGIS 3.2
• PostgreSQL 12.10 (64 bit)
  • PostGIS 3.2
• PostgreSQL 11.15 (64 bit)
  • PostGIS 3.2

PostGIS 3.3.3 is supported although is not certified.
PostGIS 3.3.3 is a minor version update.

I tested myself and I did not encounter any issue.

For example, my server is running PostgreSQL 14.8 and PostGIS 3.3.3, the latest available versions.

As you can see these versions are newer minor versions, which are supported but not certified. We need to keep PostgreSQL and PosGIS patched, it is a good practice to do so.

The only caveat is if you update the PostGIS version you must upgrade the PostGIS extension version in the PostgreSQL database running these commands.

--update postgis extension in each pg database
SELECT postgis_full_version();
ALTER EXTENSION postgis UPDATE;
SELECT postgis_extensions_upgrade();

--run one more time to check
ALTER EXTENSION postgis UPDATE;
SELECT postgis_full_version();

I hope this helps.