From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
Date: Sat, 16 Aug 2025 10:11:24 -0400
Message-ID: <757307.1755353484@sss.pgh.pa.us> (raw)
In-Reply-To: <19020-2028eba94974a545@postgresql.org>
References: <19020-2028eba94974a545@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19020: BufFileDumpBuffer writes uninitialized data on executing hash join
In-Reply-To: <757307.1755353484@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox