| From: | Marko Tiikkaja <pgmail(at)joh(dot)to> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7516: PL/Perl crash |
| Date: | 2012-09-14 08:03:12 |
| Message-ID: | 5052E4C0.2060004@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 9/13/12 11:58 PM, Tom Lane wrote:
> 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.
It does, indeed. I can't reproduce the bug on my end with that patch
applied.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sandeep Thakkar | 2012-09-14 08:14:04 | Re: initdb.exe changes --locale option |
| Previous Message | Sandeep Thakkar | 2012-09-14 07:32:37 | Re: initdb.exe changes --locale option |