postgis 3.5.0: ST_Within huge performance issue (regression?) with specific geometry (multipolygon)
Fabien Vallée <[email protected]>
| Newsgroups | gmane.comp.gis.postgis |
|---|---|
| Message-ID | <PAXPR09MB551248C4D3D6562293914E17E8232@PAXPR09MB5512.eurprd09.prod.outlook.com> |
Tested with: "POSTGIS=""3.5.0 d2c3ca4"" [EXTENSION] PGSQL=""160"" GEOS=""3.12.1-CAPI-1.18.1"" PROJ=""9.4.0 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db"" LIBXML=""2.9.14"" LIBJSON=""0.17"" LIBPROTOBUF=""1.4.1"" WAGYU=""0.5.0 (Internal)"" (core procs from ""3.4.2 c19ce56"" need upgrade)" or another server with same database: "POSTGIS=""3.5.0 d2c3ca4"" [EXTENSION] PGSQL=""170"" GEOS=""3.10.2-CAPI-1.16.0"" PROJ=""8.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db"" (compiled against PROJ 8.10.2) LIBXML=""2.9.13"" LIBJSON=""0.15"" LIBPROTOBUF=""1.3.3"" WAGYU=""0.5.0 (Internal)""" Context: departement contains only 101 geometries, but ocsge.occupation_sol is quite big (4860333 entries). BOTH SRID 4326. The geometry i'm searching within is a multipolygon (many islands) (and I don't get same behavior searching within something simpler) [cid:6c9ebb35-dd6e-47ca-a32e-dbd5808fca3d] I'm doing a simple query: select a.geometrie from ocsge.occupation_sol as a, departement as d where ST_Within( a.geometrie, d.geometrie) and d.code_insee = '29' The request was working fine before (postgis 3.4) as far as I can tell with results within a few seconds max. In that specific case, I am expecting the query to return 0 results but now (postgis 3.5) I never get any response, the request just timeout. The query is supposed to use a geometry index (gist): [cid:df1d1b40-86f6-4b78-9c7b-704102faa68c] It looks like the index is not used at all (I tried to re-index both tables, no changes). If I an intersects instead, I get results within 3 seconds: select a.geometrie from ocsge.occupation_sol as a, departement as d where ST_Intersects(a.geometrie, d.geometrie) and d.code_insee = '29' (returns 310 results) If I do both intersects + within: select a.geometrie from ocsge.occupation_sol as a, departement as d where ST_Intersects(a.geometrie, d.geometrie) and ST_Within(a.geometrie, d.geometrie) and d.code_insee = '29' I get 0 results (as expected) but it's very slow (50 secondes) (query plan attached). Testing more, I figured out that _ST_Within is working fine and is much much faster than ST_Within. Testing with same geometry (bloody Finistère) against another table (35k rows), ST_Within takes 52 seconds while _ST_Within "only" takes 13 seconds (both with 277 results). ST_Intersects takes 5s with 298 results. I've also figured out that I don't reproduce the issue testing with searching within another (much simplier) geometry. The geometry causing trouble can be downloaded (as geojson, 29MB) here: https://send.smart4.io/f.php?h=1G_6egdP&d=1 (from bdtopo database https://geoservices.ign.fr/bdtopo) Please let me know if I'm missing something or if you need anything else to investiguate. Thanks a lot, Fabien Vallée
image.png
(image/png, 39.8 KB) - not displayed
image.png
(image/png, 185 KB) - not displayed
query_plan.json
(application/json, 2 KB) - not displayed