[postgis-tickets] [PostGIS] #4890: ST_Transform large slow down from upgrade to 3.1.1 from 2.4

[PostGIS]

#4890: ST_Transform large slow down from upgrade to 3.1.1 from 2.4
-------------------------+---------------------------
  Reporter:  SAbernethy  |      Owner:  pramsey
      Type:  defect      |     Status:  new
  Priority:  blocker     |  Milestone:  PostGIS 3.1.2
 Component:  postgis     |    Version:  3.1.x
Resolution:              |   Keywords:
-------------------------+---------------------------

Comment (by mboeringa):

 Paul, I know little about PostgreSQL and PostGIS's internal working and
 even less about the development of both, but, if a full fix by somehow
 caching the transformation object at the PostgreSQL application level is
 to difficult to implement in a short period of time, would it at least
 potentially be possible to cache the transform object at the transaction
 level?

 Many systems that do mass scale updates/inserts at least batch individual
 statements in relatively large sets in one transaction.

 It would not be a solution for all problems and workflows, but would help
 quite a number of people I think.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4890#comment:10>
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.