Re: PL/Perl Does not Like vstrings

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/Perl Does not Like vstrings
Date: 2012-01-05 17:08:09
Message-ID: 4F05D8F9.3010909@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/05/2012 10:34 AM, Tom Lane wrote:
>
> Unconditional sv_mortalcopy sounds like the thing to do then, but a
> comment would help. And if this isn't a Perl bug, I would like to
> know what is.

Indeed. David, can you file a bug on this?

>
> BTW, shouldn't we be making some attempt to drop the result of the
> sv_mortalcopy? Or is it just assumed that it will be garbage-collected
> before the memory leak gets too bad?
>
>

Yes, it will be garbage collected before long. See discussion in perldoc
perlguts.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2012-01-05 17:17:42 Re: PL/Perl Does not Like vstrings
Previous Message Andrew Dunstan 2012-01-05 17:05:39 pgsql: Work around perl bug in SvPVutf8().