Andres Freund writes:
> I downloaded the RHEL6 srpm, and it appears to be patched to
> automatically disable pymalloc when running under valgrind (via
> disable-pymalloc-on-valgrind-py26.patch). That explains why you're
> seing the problem, but skink isn't (it's running debian).
Hah. I suspecte
On 2016-04-10 22:03:53 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2016-04-10 17:55:25 -0400, Tom Lane wrote:
> >> Hmm. It's true that I don't have the python debuginfo RPM installed.
> >> But this is a live bug, so I suspect you were too generous about
> >> those suppressions.
>
> > C
Andres Freund writes:
> On 2016-04-10 17:55:25 -0400, Tom Lane wrote:
>> Hmm. It's true that I don't have the python debuginfo RPM installed.
>> But this is a live bug, so I suspect you were too generous about
>> those suppressions.
> Could be - I just used the ones (after adapting for 32 vs. 64
On 2016-04-10 17:55:25 -0400, Tom Lane wrote:
> Hmm. It's true that I don't have the python debuginfo RPM installed.
> But this is a live bug, so I suspect you were too generous about
> those suppressions.
Could be - I just used the ones (after adapting for 32 vs. 64 bit
issues) provided by upstr
Andres Freund writes:
> On 2016-04-10 17:10:57 -0400, Tom Lane wrote:
>> ... I'll be fixing this one
>> shortly, but now we have another puzzle: why isn't buildfarm member
>> skink seeing the same failure? It is running the plpython tests.
> I possible that it's hidden by the broad python error
On 2016-04-10 17:10:57 -0400, Tom Lane wrote:
> After failing at that, it occurred to me to try it under valgrind,
> and kaboom! I found a *different* bug, which has apparently been
> there a long time. (I say different because I don't see how this
> one could produce tick's symptoms; it's a refe