> heap_close(rel, RowExclusiveLock);
> + heap_freetuple(tup);
> return tup->t_data->t_oid;
> }
>
> Uh, you didn't notice that the tuple you just freed is still in use
> on the next line?
That's right :-((( Will try to be a little bit more accurate.
> Memory leaks like this are not worth worrying about because the memory
> will be reclaimed at end of transaction --- maybe even sooner after
> I improve the memory-context handling.
But anyway it is better to free memory, because transaction can be quite large.
New patch attached.
BTW, could you please say what memory leaks can be safely ignored.
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------