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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: exclusion(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
Date: 2025-08-16 14:11:24
Message-ID: 757307.1755353484@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message vignesh C 2025-08-17 13:53:18 Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
Previous Message Arseniy Mukhin 2025-08-16 12:07:47 Re: BUG #19018: high memory usage and "stack depth limit exceeded", with GiST index on ltree