pgsql: Fix valgrind failure - Mailing list pgsql-committers

From Álvaro Herrera
Subject pgsql: Fix valgrind failure
Date
Msg-id E1wA2Wz-003N0N-2Y@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Fix valgrind failure
List pgsql-committers
Fix valgrind failure

Buildfarm member skink reports that the new REPACK code is trying to
write uninitialized bytes to disk, which correspond to padding space in
the SerializedSnapshotData struct.  Silence that by initializing the
memory in SerializeSnapshot() to all zeroes.

Co-authored-by: Srinath Reddy Sadipiralla <srinath2133@gmail.com>
Co-authored-by: Álvaro Herrera <alvherre@kurilemu.de>
Discussion: https://postgr.es/m/1976915.1775537087@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5bcc3fbd196ccbec55c2ce6b58d6946f06cf6213

Modified Files
--------------
src/backend/commands/repack_worker.c | 2 +-
src/backend/utils/time/snapmgr.c     | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: John Naylor
Date:
Subject: pgsql: Use .h for the file containing the page checksum code fragment
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Add isolation tests for UPDATE/DELETE FOR PORTION OF