[postgis-tickets] [PostGIS] #5387: ST_Transform(geom, str, str) is very slow
PostGIS
trac at osgeo.org
Mon Jun 19 13:43:48 PDT 2023
#5387: ST_Transform(geom, str, str) is very slow
-------------------------+---------------------------
Reporter: cdestigter | Owner: pramsey
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 3.4.0
Component: postgis | Version: 3.3.x
Resolution: | Keywords:
-------------------------+---------------------------
Comment (by cdestigter):
Yes - but it doesn't make sense to have to sync up the SRIDs in that table
with the systems in proj.db. Apart from any other concerns, we'd have to
find and use some form of integer IDs for them - and not all of them are
EPSG CRSes. In addition the Postgres database is not deployed concurrently
with the proj.db in our app images and so trying to keep them in sync
would require complex migrations, which can be avoided if we skip using
spatial_ref_sys at all.
I feel like that concern is tangential - the issue I had in this ticket is
that some forms of the ST_Transform() function are very slow - presumably
they are not caching their transforms across multiple input rows. Can this
be improved?
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5387#comment:8>
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.
More information about the postgis-tickets
mailing list