[postgis-tickets] [PostGIS] #5025: Inconsistent behavior with ST_Within across versions

[PostGIS]

#5025: Inconsistent behavior with ST_Within across versions
----------------------+---------------------------
  Reporter:  byrman   |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 3.0.6
 Component:  postgis  |    Version:  3.1.x
Resolution:           |   Keywords:
----------------------+---------------------------
Comment (by robe):

 For POSTGIS="3.2.1 3.2.1" [EXTENSION] PGSQL="140"
 GEOS="3.10.2-CAPI-1.16.0" PROJ="7.2.1" GDAL="GDAL 3.4.2, released
 2022/03/08" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.5.0
 (Internal)" RASTER PostgreSQL 14.1, compiled by Visual C++ build 1914,
 64-bit

 My answers agree with yours, 50 with an index and 100 if I drop the
 a_3d_idx. I also get 100 if I keep the a_3d_idx and drop the b_2d_idx.


 For

 POSTGIS="2.5.7dev r17978" [EXTENSION] PGSQL="120" GEOS="3.8.3-CAPI-1.13.4"
 PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.3.3, released
 2021/10/25" LIBXML="2.7.8" LIBJSON="0.12" LIBPROTOBUF="1.2.1" RASTER
 PostgreSQL 12.2, compiled by Visual C++ build 1914, 64-bit

 I am getting 100 for both cases.

 I suspect this has to do with the instrumentation use for PostgreSQL 12
 and above introduced in PostGIS 3.0.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5025#comment:4>
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.