PostgreSQL Enterprise Geodatabase performance using PG_GEOMETRY

285
3
Jump to solution
01-06-2022 12:07 PM
Labels (3)
ClaudioRuschel
New Contributor III

I have been using by default the "PG_GEOMETRY" type to store features in Enterprise Geodatabase hosted in PostgreSQL. This strategy is very interesting when building and loading the database. But, in a production environment where most feature classes are accessed by geoservices in read-only mode, can the difference in the performance of accessing features kept in "PG_GEOMETRY" compared to "ST_GEOMETRY" be significant? 

0 Kudos
1 Solution

Accepted Solutions
George_Thompson
Esri Frequent Contributor

Thanks for the additional information. I have not heard of ArcGIS converting PG --> ST before.

In terms of performance, I would say that they are "equal" depending on many factors. The ArcGIS clients will work with both.

The best course of action would be to do some testing within your environment. I have seen clients use both formats within the same Enterprise Geodatabase based on the need.

Others may be able to chime in on what they have seen.

--- George T.

View solution in original post

3 Replies
George_Thompson
Esri Frequent Contributor

I think that we would need some more details on the clients accessing the data, data type (point / lines / polys), any advanced behavior, etc.

Do you have updated indexes / statistics?

Is the data editing / updated often?

Any additional details would be helpful.

--- George T.
0 Kudos
ClaudioRuschel
New Contributor III

George, it is a general question. The geodatabases that I´m mentioning usually support applications like spatial data infrastructures with hundred of geoservices acccessing feature layers, almost allways on a read-only way. I once read a long time ago that internally ArcGIS would convert the PostGIS format to ST_Geometry for any operation. In other words, theoretically there would be a performance difference considering the same server environment and changing only the storage format. I have not found this issue documented in current versions of Enterprise Geodatabase. Therefore, I am questioning whether, in practice, there might be any noticeable difference in the performance of a geoservice considering only the variation of the geometry's storage format type.

0 Kudos
George_Thompson
Esri Frequent Contributor

Thanks for the additional information. I have not heard of ArcGIS converting PG --> ST before.

In terms of performance, I would say that they are "equal" depending on many factors. The ArcGIS clients will work with both.

The best course of action would be to do some testing within your environment. I have seen clients use both formats within the same Enterprise Geodatabase based on the need.

Others may be able to chime in on what they have seen.

--- George T.