Stop using the non-reentrant version of GEOS C-API functions
Everytime I add something new to GEOS question myself about adding or not the non-reentrant signature, and everytime I tell to myself: PostGIS ain't ready for that…
Guess it's about time to get ready!
Being there GEOS calls in liblwgeom, this might mean having a "liblwgeom" context too, which btw is also useful for other things (reentrancy of error messages!).
Change History
(5)
Milestone: |
PostGIS 2.3.0 → PostGIS 2.4.0
|
Milestone: |
PostGIS 2.4.0 → PostGIS 2.5.0
|
Milestone: |
PostGIS 2.5.0 → PostGIS 3.0.0
|
Milestone: |
PostGIS 3.0.0 → PostGIS 3.1.0
|
Milestone: |
PostGIS 3.1.0 → PostGIS Fund Me
|