1 # This is a suppression file for use with Valgrind tools. File format
3 # http://valgrind.org/docs/manual/mc-manual.html#mc-manual.suppfiles
5 # The libc symbol that implements a particular standard interface is
6 # implementation-dependent. For example, strncpy() shows up as "__GI_strncpy"
7 # on some platforms. Use wildcards to avoid mentioning such specific names.
10 # We have occasion to write raw binary structures to disk or to the network.
11 # These may contain uninitialized padding bytes. Since recipients also ignore
12 # those bytes as padding, this is harmless.
26 socketcall.sendto(msg)
38 fun:pgstat_write_statsfiles
42 padding_XLogRecData_CRC
49 padding_XLogRecData_write
63 fun:write_relcache_init_file
67 # gcc on ppc64 can generate a four-byte read to fetch the final "char" fields
68 # of a FormData_pg_cast. This is valid compiler behavior, because a proper
69 # FormData_pg_cast has trailing padding. Tuples we treat as structures omit
70 # that padding, so Valgrind reports an invalid read. Practical trouble would
71 # entail the missing pad bytes falling in a different memory page. So long as
72 # the structure is aligned, that will not happen.
74 overread_tuplestruct_pg_cast