Re: BUG #9223: plperlu result memory leak
От
Alex Hunsaker
Тема
Re: BUG #9223: plperlu result memory leak
Дата
Msg-id
CAFaPBrSpM+uhbe4J1ayQMAqj_Q0rvup=j0Y76WsSdfxpy_E7xw@mail.gmail.com
Ответ на
Re: [BUGS] BUG #9223: plperlu result memory leak (Sergey Burladyan)
Список
Дерево обсуждения
BUG #9223: plperlu result memory leak eshkinkot@gmail.com
Re: BUG #9223: plperlu result memory leak Sergey Burladyan <eshkinkot@gmail.com>
Re: BUG #9223: plperlu result memory leak Alex Hunsaker <badalex@gmail.com>
Re: BUG #9223: plperlu result memory leak Alvaro Herrera <alvherre@2ndquadrant.com>
Re: BUG #9223: plperlu result memory leak Alex Hunsaker <badalex@gmail.com>
Re: BUG #9223: plperlu result memory leak Alex Hunsaker <badalex@gmail.com>
Re: BUG #9223: plperlu result memory leak Alvaro Herrera <alvherre@2ndquadrant.com>
Re: BUG #9223: plperlu result memory leak Sergey Burladyan <eshkinkot@gmail.com>
Re: BUG #9223: plperlu result memory leak Sergey Burladyan <eshkinkot@gmail.com>
On Tue, Feb 25, 2014 at 6:56 AM, Sergey Burladyan wrote: > It looks like I found the problem, Perl use reference count and something that > is called "Mortal" for memory management. As I understand it, mortal is free > after FREETMPS. Plperl call FREETMPS in plperl_call_perl_func() but after it, > plperl ask perl interpreter again for new mortal SV variables, for example, in > hek2cstr from plperl_sv_to_datum, and this new SV is newer freed. So I think hek2cstr is the only place we leak (its the only place I can see that allocates a mortal sv without being wrapped in ENTER/SAVETMPS/FREETMPS/LEAVE). Does the attached fix it for you?
В списке pgsql-bugs по дате отправления