Monday, December 12, 2011, 12:33:03 PM you wrote:
> On 12.12.2011 13:16, Matteo Beccati wrote:
>> Just to clarify, am I correct assuming that the issue does not affect
>> tables which have non-indexed inet fields?
> Hmm, I think it might also affect queries that do large merge joins on
> inet fields. Not sure about that. In any case, it's a memory leak that
> gets cleared at the end of statement, so it can only become a problem
> when dealing with large data sets.
The second test case I originally sent uses inet-functions in a complicated
query, and it also shows the described behaviour.
So the problem is not limited to indexes, but also will appear in queries!
--
Jochen Erwied | home: jochen@erwied.eu +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 | work: joe@mbs-software.de +49-2151-7294-24, FAX: -50
D-45470 Muelheim | mobile: jochen.erwied@vodafone.de +49-173-5404164
