Add valgrind suppressions for bootstrap related code.

Author: Andres Freund
Backpatch: 9.4, where we started to maintain valgrind suppressions

1 files changed, 42 insertions, 0 deletions

diff --git a/src/tools/valgrind.supp b/src/tools/valgrind.supp
index 91742d790bc..0e62782248f 100644
--- a/src/tools/valgrind.supp
+++ b/src/tools/valgrind.supp
@@ -92,6 +92,48 @@
 }
 
 
+{
+	padding_bootstrap_initial_xlog_write
+	Memcheck:Param
+	write(buf)
+
+	...
+	fun:BootStrapXLOG
+}
+
+{
+	padding_bootstrap_initial_xlog_CRC
+	Memcheck:Value8
+	fun:BootStrapXLOG
+	fun:AuxiliaryProcessMain
+}
+
+{
+	padding_bootstrap_control_file_write
+	Memcheck:Param
+	write(buf)
+
+	...
+	fun:WriteControlFile
+	fun:BootStrapXLOG
+}
+
+{
+	padding_bootstrap_control_file_CRC
+	Memcheck:Value8
+	fun:WriteControlFile
+	fun:BootStrapXLOG
+}
+
+{
+	bootstrap_write_relmap_overlap
+	Memcheck:Overlap
+	fun:memcpy*
+	fun:write_relmap_file
+	fun:RelationMapFinishBootstrap
+}
+
+
 # gcc on ppc64 can generate a four-byte read to fetch the final "char" fields
 # of a FormData_pg_cast.  This is valid compiler behavior, because a proper
 # FormData_pg_cast has trailing padding.  Tuples we treat as structures omit