[postgis-devel] lwgeom_release WTF

[Mark Cave-Ayland]

strk wrote:

> Right. This is basically a memory optimization as most of the times
> (when under postgres umbrella) the actual BIG THINGS are kept serialized
> in the detoasted datum, so would get released by postgres pools.
> 
> The plan for release_deep/clone_deep was for extra-postgres use
> (standalone liblwgeom).

I see. So you're saying that the POINTARRAYs are effectively pointers 
into the serialized set of points within the Datum? This would explain 
why the PIP code leaks so much, since normally any geometries returned 
as a SELECT function will be freed automatically when the executor has 
finished with them. The PIP code however, generates its structures 
internally and so must responsible for clearing them itself.


ATB,

Mark.

-- 
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063