Skip site navigation (1) Skip section navigation (2)

Re: BUG #7516: PL/Perl crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Tiikkaja <pgmail(at)joh(dot)to>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7516: PL/Perl crash
Date: 2012-09-13 21:58:52
Message-ID: 22854.1347573532@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: 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


In response to

Responses

pgsql-bugs by date

Next:From: dfisupportDate: 2012-09-13 22:50:31
Subject: BUG #7537: Server will not start up from Windows Service Manager
Previous:From: Tom LaneDate: 2012-09-13 21:42:02
Subject: Re: BUG #7516: PL/Perl crash

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group