Request a Demo
Home   >   mailing lists

Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
Date
Msg-id 757307.1755353484@sss.pgh.pa.us
Whole thread Raw
In response to BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view 
PG Bug reporting form <noreply@postgresql.org> writes:
> ==00:00:00:06.424 2914013== Syscall param pwrite64(buf) points to
> uninitialised byte(s)
> ==00:00:00:06.424 2914013==    at 0x4FF8517: pwrite (pwrite64.c:25)
> ==00:00:00:06.424 2914013==    by 0x7C10E8: pg_pwritev (pg_iovec.h:101)
> ==00:00:00:06.424 2914013==    by 0x7C3BD1: FileWriteV (fd.c:2293)
> ==00:00:00:06.424 2914013==    by 0x7BEB0A: FileWrite (fd.h:219)
> ==00:00:00:06.424 2914013==    by 0x7BF685: BufFileDumpBuffer
> (buffile.c:538)

Looks like this path needs to be added to the suppressions in
src/tools/valgrind.supp.  I'm a bit surprised that the buildfarm
hasn't already shown this up.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Arseniy Mukhin
Date:
Subject: Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree