| 1 |
# This is a suppression file for use with Valgrind tools. File format |
| 2 |
# documentation: |
| 3 |
# http://valgrind.org/docs/manual/mc-manual.html#mc-manual.suppfiles |
| 4 |
|
| 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. |
| 8 |
# Avoid mentioning functions that are good candidates for inlining, |
| 9 |
# particularly single-caller static functions. Suppressions mentioning them |
| 10 |
# would be ineffective at higher optimization levels. |
| 11 |
|
| 12 |
|
| 13 |
# We have occasion to write raw binary structures to disk or to the network. |
| 14 |
# These may contain uninitialized padding bytes. Since recipients also ignore |
| 15 |
# those bytes as padding, this is harmless. |
| 16 |
|
| 17 |
{ |
| 18 |
padding_pgstat_write |
| 19 |
Memcheck:Param |
| 20 |
write(buf) |
| 21 |
|
| 22 |
... |
| 23 |
fun:pgstat_write_statsfiles |
| 24 |
} |
| 25 |
|
| 26 |
{ |
| 27 |
padding_XLogRecData_CRC |
| 28 |
Memcheck:Value8 |
| 29 |
|
| 30 |
fun:pg_comp_crc32c* |
| 31 |
fun:XLogRecordAssemble |
| 32 |
} |
| 33 |
|
| 34 |
{ |
| 35 |
padding_XLogRecData_write |
| 36 |
Memcheck:Param |
| 37 |
pwrite64(buf) |
| 38 |
|
| 39 |
... |
| 40 |
fun:XLogWrite |
| 41 |
} |
| 42 |
|
| 43 |
{ |
| 44 |
padding_relcache |
| 45 |
Memcheck:Param |
| 46 |
write(buf) |
| 47 |
|
| 48 |
... |
| 49 |
fun:write_relcache_init_file |
| 50 |
} |
| 51 |
|
| 52 |
{ |
| 53 |
padding_reorderbuffer_serialize |
| 54 |
Memcheck:Param |
| 55 |
write(buf) |
| 56 |
|
| 57 |
... |
| 58 |
fun:ReorderBufferSerializeTXN |
| 59 |
} |
| 60 |
|
| 61 |
{ |
| 62 |
padding_twophase_prepare |
| 63 |
Memcheck:Param |
| 64 |
write(buf) |
| 65 |
|
| 66 |
... |
| 67 |
fun:EndPrepare |
| 68 |
} |
| 69 |
|
| 70 |
|
| 71 |
{ |
| 72 |
padding_twophase_CRC |
| 73 |
Memcheck:Value8 |
| 74 |
fun:pg_comp_crc32c* |
| 75 |
fun:EndPrepare |
| 76 |
} |
| 77 |
|
| 78 |
{ |
| 79 |
padding_bootstrap_initial_xlog_write |
| 80 |
Memcheck:Param |
| 81 |
write(buf) |
| 82 |
|
| 83 |
... |
| 84 |
fun:BootStrapXLOG |
| 85 |
} |
| 86 |
|
| 87 |
{ |
| 88 |
padding_bootstrap_control_file_write |
| 89 |
Memcheck:Param |
| 90 |
write(buf) |
| 91 |
|
| 92 |
... |
| 93 |
fun:WriteControlFile |
| 94 |
fun:BootStrapXLOG |
| 95 |
} |
| 96 |
|
| 97 |
{ |
| 98 |
bootstrap_write_relmap_overlap |
| 99 |
Memcheck:Overlap |
| 100 |
fun:memcpy* |
| 101 |
fun:write_relmap_file |
| 102 |
fun:RelationMapFinishBootstrap |
| 103 |
} |
| 104 |
|
| 105 |
|
| 106 |
# gcc on ppc64 can generate a four-byte read to fetch the final "char" fields |
| 107 |
# of a FormData_pg_cast. This is valid compiler behavior, because a proper |
| 108 |
# FormData_pg_cast has trailing padding. Tuples we treat as structures omit |
| 109 |
# that padding, so Valgrind reports an invalid read. Practical trouble would |
| 110 |
# entail the missing pad bytes falling in a different memory page. So long as |
| 111 |
# the structure is aligned, that will not happen. |
| 112 |
{ |
| 113 |
overread_tuplestruct_pg_cast |
| 114 |
Memcheck:Addr4 |
| 115 |
|
| 116 |
fun:IsBinaryCoercibleWithCast |
| 117 |
} |
| 118 |
|
| 119 |
# Python's allocator does some low-level tricks for efficiency. Those |
| 120 |
# can be disabled for better instrumentation; but few people testing |
| 121 |
# postgres will have such a build of python. So add broad |
| 122 |
# suppressions of the resulting errors. |
| 123 |
# See also https://svn.python.org/projects/python/trunk/Misc/README.valgrind |
| 124 |
{ |
| 125 |
python_clever_allocator |
| 126 |
Memcheck:Addr4 |
| 127 |
fun:PyObject_Free |
| 128 |
} |
| 129 |
|
| 130 |
{ |
| 131 |
python_clever_allocator |
| 132 |
Memcheck:Addr8 |
| 133 |
fun:PyObject_Free |
| 134 |
} |
| 135 |
|
| 136 |
{ |
| 137 |
python_clever_allocator |
| 138 |
Memcheck:Value4 |
| 139 |
fun:PyObject_Free |
| 140 |
} |
| 141 |
|
| 142 |
{ |
| 143 |
python_clever_allocator |
| 144 |
Memcheck:Value8 |
| 145 |
fun:PyObject_Free |
| 146 |
} |
| 147 |
|
| 148 |
{ |
| 149 |
python_clever_allocator |
| 150 |
Memcheck:Cond |
| 151 |
fun:PyObject_Free |
| 152 |
} |
| 153 |
|
| 154 |
{ |
| 155 |
python_clever_allocator |
| 156 |
Memcheck:Addr4 |
| 157 |
fun:PyObject_Realloc |
| 158 |
} |
| 159 |
|
| 160 |
{ |
| 161 |
python_clever_allocator |
| 162 |
Memcheck:Addr8 |
| 163 |
fun:PyObject_Realloc |
| 164 |
} |
| 165 |
|
| 166 |
{ |
| 167 |
python_clever_allocator |
| 168 |
Memcheck:Value4 |
| 169 |
fun:PyObject_Realloc |
| 170 |
} |
| 171 |
|
| 172 |
{ |
| 173 |
python_clever_allocator |
| 174 |
Memcheck:Value8 |
| 175 |
fun:PyObject_Realloc |
| 176 |
} |
| 177 |
|
| 178 |
{ |
| 179 |
python_clever_allocator |
| 180 |
Memcheck:Cond |
| 181 |
fun:PyObject_Realloc |
| 182 |
} |
| 183 |
|
| 184 |
# NUMA introspection requires touching memory first, and some of it may |
| 185 |
# be marked as noacess (e.g. unpinned buffers). So just ignore that. |
| 186 |
{ |
| 187 |
pg_numa_touch_mem_if_required |
| 188 |
Memcheck:Addr4 |
| 189 |
fun:pg_numa_touch_mem_if_required |
| 190 |
} |
| 191 |
|
| 192 |
{ |
| 193 |
pg_numa_touch_mem_if_required |
| 194 |
Memcheck:Addr8 |
| 195 |
fun:pg_numa_touch_mem_if_required |
| 196 |
} |