#3865 closed defect (fixed)
Build Request
Reported by: | ravelllott | Owned by: | robe |
---|---|---|---|
Priority: | low | Milestone: | PostGIS 2.3.4 |
Component: | postgis | Version: | 2.3.x |
Keywords: | build request | Cc: |
Description
We have been running 2.1.7 postgis with postgres 9.4.3 for a few years. we upgraded to 9.6 and 2.2.3 respectively. and one of our queries has suffered a 300 percent increase in processing time ~60 seconds to ~180 seconds.
I was hoping to request a windows x64 build of 2.1.9 built against postgres 9.6.X.
Change History (6)
comment:2 by , 7 years ago
Milestone: | PostGIS PostgreSQL → PostGIS 2.3.4 |
---|
comment:3 by , 7 years ago
Owner: | changed from | to
---|
comment:4 by , 7 years ago
We did try the 2.4.0 RC2 build and it appears to not have the performance degradation.
Also we believed to have tracked down the issue to ST_Intersects.
comment:5 by , 7 years ago
Priority: | high → low |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
you upgraded to 2.2.3 or 2.3.3?
I can't build a 2.1.9 for PostgreSQL 9.6 because 2.1 only goes thru support of 9.4. Actually doesn't compile against 9.6 as I recall.
See the matrix.
https://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS
Now if you can provide a query of what slowed down, we can look at it and perhaps release a fix for 2.3.4.
Would also help if you can show output of: