aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-03-07 13:25:11 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-03-07 13:29:49 +0200
commit080ad9120d79933e5aed545986885058f8aa7385 (patch)
tree922e25b81525dd748f13f914c408609919f08f0f /src/backend/access/gist/gistproc.c
parentc7a186e392d4654148a45eaf8ffbf026553ecbdb (diff)
downloadpostgresql-080ad9120d79933e5aed545986885058f8aa7385.tar.gz
postgresql-080ad9120d79933e5aed545986885058f8aa7385.zip
Fix dangling smgr_owner pointer when a fake relcache entry is freed.
A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently hasn't caused crashes in practice, or we would've heard about it earlier. Andres found this with Valgrind. Report and fix by Andres Freund, with minor modifications by me. Backpatch to all supported versions.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions