[postgis-devel] Issue 57 in postgis: Re-work prepared geometry to use a custom memory context

[codesite-noreply at google.com]

Issue 57: Re-work prepared geometry to use a custom memory context
http://code.google.com/p/postgis/issues/detail?id=57

New issue report by pwramsey3:
By using a custom memory context underneath the function manager context,
we can free the GEOS objects cleanly at the end of the statement. Right now
the GEOS objects are directly inside the fmgr context, so there's no way to
clean them up before the context is freed. See the transform() code for an
example.

Until this is done, the preparedgeometry will leak two objects for every
SQL call, no matter how clean GEOS gets.



Issue attributes:
	Status: Accepted
	Owner: pwramsey3
	Labels: Type-Defect Priority-Medium

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings