[PostGIS] #5815: hash operator error

[PostGIS]

#5815: hash operator error
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  PostGIS 3.5.1
 Component:  postgis  |    Version:  3.4.x
Resolution:           |   Keywords:
----------------------+---------------------------
Comment (by robe):

 Replying to [comment:4 pramsey]:
 > New and exciting error. On 3.4 it's a different error. So this may have
 never worked, and is now just failing in a different way.
 > {{{
 > postgis34=# WITH lines AS (SELECT ST_GeomFromText('LINESTRING(1 2, 3
 4)') AS geom
 >  UNION ALL
 >   SELECT  ST_GeomFromText('LINESTRING(6 5, 7 8)') AS geom
 >  )
 >  SELECT t1.geom, t2.geom
 >  FROM lines AS t1, lines AS t2
 >  WHERE t1.geom <> t2.geom;
 >
 > ERROR:  operator is not unique: geometry <> geometry
 > LINE 7: WHERE t1.geom <> t2.geom;                      ^
 > HINT:  Could not choose a best candidate operator. You might need to add
 explicit type casts.
 > }}}

 I think the addition of the operator you added in 3.5, that was the error
 we used to get

 see
 https://git.osgeo.org/gitea/postgis/postgis/src/branch/stable-3.5/NEWS#L111

 So I think the fix for #5175  is what is causing this error
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5815#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.