aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-08-02 19:43:04 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2025-08-02 21:59:46 -0400
commit2c7b4ad24dda86a73d80df063e9a56c3ecb1e4bb (patch)
treeebe0cc0d7035d0a59f02e0b0e3d8dbb01cee15db /src/backend/executor/nodeModifyTable.c
parent9f18fa9995628fef752d704d874eeed0bab815e5 (diff)
downloadpostgresql-2c7b4ad24dda86a73d80df063e9a56c3ecb1e4bb.tar.gz
postgresql-2c7b4ad24dda86a73d80df063e9a56c3ecb1e4bb.zip
Suppress complaints about leaks in function cache loading.
PL/pgSQL and SQL-function parsing leak some stuff into the long-lived function cache context. This isn't really a huge practical problem, since it's not a large amount of data and the cruft will be recovered if we have to re-parse the function. It's not clear that it's worth working any harder than the previous patch did to eliminate these leak complaints, so instead silence them with a suppression rule. This suppression rule also hides the fact that CachedFunction structs are intentionally leaked in some cases because we're unsure if any fn_extra pointers remain. That might be nice to do something about eventually, but it's not clear how. Author: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/285483.1746756246@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions