[postgis-tickets] [PostGIS] #4750: Performance issue with computed columns

[PostGIS]

#4750: Performance issue with computed columns
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  high     |  Milestone:  PostGIS 3.0.3
 Component:  postgis  |    Version:  3.0.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 okay got excited too quickly.  I have to recheck but it seemed like

 1) Creating the new computed column and using it was fast 1 secs 208 ms
 2) But then I ran the query against the old computed column and it too was
 fast ` 1 secs 300 ms

 3) Recreating the table and adding in the 2 new computed columns with the
 index, and doing a vacuum (analyze,verbose) test.co_random_points.

 Then running the query testing both computed columns, they are back to 30
 secs to complete.
 I'm going to revisit this to see if they become fast again.  Maybe some
 external process is fixing things.

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