aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-11-05 09:40:55 +0900
committerMichael Paquier <michael@paquier.xyz>2024-11-05 09:40:55 +0900
commit7f3b41ce48a58f090da94dbcc737483c217ce9c3 (patch)
tree5bbf159064d56c46542a171011b617250ceb5232 /src/backend/executor
parent811f8d3f10a448644004954ad784bed4d51b88c7 (diff)
downloadpostgresql-7f3b41ce48a58f090da94dbcc737483c217ce9c3.tar.gz
postgresql-7f3b41ce48a58f090da94dbcc737483c217ce9c3.zip
Clear padding of PgStat_HashKey when handling pgstats entries
PgStat_HashKey is currently initialized in a way that could result in random data if the structure has any padding bytes. The structure has no padding bytes currently, fortunately, but it could become a problem should the structure change at some point in the future. The code is changed to use some memset(0) so as any padding would be handled properly, as it would be surprising to see random failures in the pgstats entry lookups. PgStat_HashKey is a structure internal to pgstats, and an ABI change could be possible in the scope of a bug fix, so backpatch down to 15 where this has been introduced. Author: Bertrand Drouvot Reviewed-by: Jelte Fennema-Nio, Michael Paquier Discussion: https://postgr.es/m/Zyb7RW1y9dVfO0UH@ip-10-97-1-34.eu-west-3.compute.internal Backpatch-through: 15
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions