As described in https://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS the combination PostgreSQL 10+ requires PostGIS >= 2.3. This means that for PostgisPG10Dialect Wkb.Dialect.POSTGIS_EWKB_2 should be used instead of Wkb.Dialect.POSTGIS_EWKB_1 since EWKB_1 is the dialect for Postgis version < 2.2.1.

However it looks like Wkb.Dialect.POSTGIS_EWKB_1 is used in multiple places when using PostgisPG10Dialect:

• it is hardcoded in the ValueBinder instead of using `this.wkbDialect` (https://github.com/hibernate/hibernate-orm/blob/c3631970a5d1d445adafc07b0632181c18c1ae8d/hibernate-spatial/src/main/java/org/hibernate/spatial/dialect/postgis/PGGeometryTypeDescriptor.java#L127-L135)

• registerColumnType in PostgisPG10Dialect (https://github.com/hibernate/hibernate-orm/blob/c3631970a5d1d445adafc07b0632181c18c1ae8d/hibernate-spatial/src/main/java/org/hibernate/spatial/dialect/postgis/PostgisPG10Dialect.java#L22-L25)

• contributeTypes in PostgisPG10Dialect via PostgisSupport (https://github.com/hibernate/hibernate-orm/blob/c3631970a5d1d445adafc07b0632181c18c1ae8d/hibernate-spatial/src/main/java/org/hibernate/spatial/dialect/postgis/PostgisSupport.java#L40-L41)

I noticed this when I tried to store an empty point in a column of type `GEOMETRY(POINT, 4326)`.

This caused the following SQL error:

Which is exactly as decribed what happens when using the POSTGIS_EWKB1 dialect: