[PostGIS] #5974: Add matching finishGEOS() to all initGEOS()

[PostGIS]

#5974: Add matching finishGEOS() to all initGEOS()
--------------------------+---------------------------
  Reporter:  ezimanyi     |      Owner:  pramsey
      Type:  enhancement  |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 3.6.1
 Component:  postgis      |    Version:  3.5.x
Resolution:               |   Keywords:
--------------------------+---------------------------
Comment (by pramsey):

 How do you mean "not formally needed for PostgreSQL"? If a bare initGEOS
 call is leaking memory it is doing it in the postgis directory too, and
 GEOS calls are not subject to the PgSQL memory manager. The implication
 would be that we have backends slowly growing, but I haven't seen that.
 Once apon a time everything run through cunit was memory clean, confirmed
 by valgrind, has that changed? If so, the change would probably be
 associated with a particular GEOS version? I would like to characterize
 this a little more before fixing it, because it isn't intuitive that we've
 been living with a memory leak forever.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5974#comment:3>
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.