Horton

Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2025-08-16T14:11:24Z
Lists: pgsql-bugs 
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