On 12/12/2011 09:29, Heikki Linnakangas wrote:
> On 12.12.2011 08:26, Tom Lane wrote:
>> Andres Freund<andres(at)anarazel(dot)de> writes:
>>> In 3b8161723c645853021b57330dd2ea0484ec6131 Heikki made DatumGetInetP
>>> toasted values. Unfortunately the btree support functions for the
>>> inet type
>>> didn't free memory which they have to do in contrast to about
>>> everything else.
>>> I fixed a few more functions than strictly necessary but I guess
>>> thats ok.
>> Seems like the correct fix is to revert these functions to the former
>> behavior, ie they should be using the PP macros not the unpacking ones.
> Agreed, there's no need to unpack here. Fixed, thanks for the report!
Just to clarify, am I correct assuming that the issue does not affect
tables which have non-indexed inet fields?
Development & Consulting - http://www.beccati.com/
In response to
pgsql-bugs by date
|Next:||From: Heikki Linnakangas||Date: 2011-12-12 11:33:03|
|Subject: Re: Postgresql 9.1.2 - abnormal memory usage|
|Previous:||From: vbberdin||Date: 2011-12-12 09:09:10|
|Subject: BUG #6331: Cross compile error/aborts. Works if '--disable-spinlock'is used|