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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
