On 10/24/2014 05:40 PM, Andres Freund wrote:
On 2014-10-24 17:13:49 +0300, Heikki Linnakangas wrote:
Yeah. The padding bytes in TwoPhaseFileHeader were not initialized.
That's simple enough to fix, but when I run valgrind, I get a lot whole
bunch of similar messages. A few are from pgstat: the
On 2014-10-24 17:13:49 +0300, Heikki Linnakangas wrote:
> Yeah. The padding bytes in TwoPhaseFileHeader were not initialized.
>
> That's simple enough to fix, but when I run valgrind, I get a lot whole
> bunch of similar messages. A few are from pgstat: the padding bytes in the
> pgstat messages a
On 10/11/2014 10:20 PM, Bruce Momjian wrote:
Uh, was this fixed. I see a cleanup commit for this C file, but this
report is from June:
commit 07a4a93a0e35a778c77ffbbbc18de29e859e18f0
Author: Heikki Linnakangas
Date: Fri May 16 09:47:50 2014 +0300
Uh, was this fixed. I see a cleanup commit for this C file, but this
report is from June:
commit 07a4a93a0e35a778c77ffbbbc18de29e859e18f0
Author: Heikki Linnakangas
Date: Fri May 16 09:47:50 2014 +0300
Initialize tsId and dbId fields in WAL record
Hi,
I've just rerun valgrind for the first time in a while and saw the
following splat. My guess is it exists since bb38fb0d43c, but that's
blindly guessing:
==2049== Use of uninitialised value of size 8
==2049==at 0x4FE66D: EndPrepare (twophase.c:1063)
==2049==by 0x4F231B: PrepareTransac
