Re: BUG #7516: PL/Perl crash - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #7516: PL/Perl crash
Date
Msg-id 22854.1347573532@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #7516: PL/Perl crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #7516: PL/Perl crash  (Marko Tiikkaja <pgmail@joh.to>)
List pgsql-bugs
I wrote:
> A probably less costly solution than marking current_call_data volatile
> is just to make it not-static.

And on still further investigation, the patch I just applied to HEAD
seems to make it go away too.  Bizarre as can be.  If that holds up for
you, I think back-patching that change is less ugly than making the
variable non-static.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #7516: PL/Perl crash
Next
From: te
Date:
Subject: how to proccess record returning null