Creating feature classes with the POSTGIS geometry type reports an incorrect SRID or fails when using PostGIS 3.5.3

Description

The PostGIS 3.5.3 release introduces modifications that prevent the successful creation of feature classes that use the PostGIS geometry type in enterprise geodatabases and databases on PostgreSQL.

Enterprise geodatabases on PostgreSQL

Using ArcGIS Pro to load or create feature classes in an enterprise geodatabase with the PostGIS geometry type appears to be successful. For example, the following output feature class shown in the next image successfully shows the correct spatial reference: SRID 3857 (WGS 1984 Web Mercator).

However, the PostGIS geometry_columns metadata reports an incorrect SRID of 0, as shown in the following image.

Databases on PostgreSQL

Using ArcGIS Pro to load feature classes into a database with the PostGIS geometry type fails with a check constraint violation error. The following error is also encountered when using PostGIS 3.6.0:

Error returned when copying and pasting a feature class into a database:

ERROR 000260: A check constraint violation has occurred.[ERROR:  new 
row for relation "botswana_tpoint" violates check constraint 
"enforce_srid_shape" DETAIL:  Failing row contains (1, Botswana, BWA, 
Africa, Primary land, 5, Botswana, 1, 010100000038014D54A338444150840D3F9E6043C1).:SQLSTATE=23514]--A check 
constraint violation has occurred.

ArcGIS Enterprise on Kubernetes deployments using a cloud relational store

ArcGIS Enterprise on Kubernetes allows organizations to configure the relational store using a cloud database service. For organizations who have configured a cloud relational store, it is important to ensure that the PostGIS extension used is not 3.5.3 or 3.6.0.

Solution or Workaround

ArcGIS Pro and ArcGIS Enterprise support PostGIS 3.x, except for versions 3.5.3 and 3.6.0, which are not supported due to PostGIS issue #5978. This issue is resolved in PostGIS versions 3.5.4 and 3.6.1