aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/cache/relcache.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-06-11 19:17:50 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-06-11 19:17:50 -0400
commitb10edaf4bb4473adc897f5643ede8c9100abddce (patch)
tree59bfe9148fb09e44d17c095789879babac614a93 /src/backend/utils/cache/relcache.c
parent858571843c8affff5a69527faa3e57f8adfa4165 (diff)
downloadpostgresql-b10edaf4bb4473adc897f5643ede8c9100abddce.tar.gz
postgresql-b10edaf4bb4473adc897f5643ede8c9100abddce.zip
Fix access to just-closed relcache entry.
It might be impossible for this to cause a problem in non-debug builds, since there'd be no opportunity for the relcache entry to get recycled before the fetch. It blows up nicely with -DRELCACHE_FORCE_RELEASE plus valgrind, though. Evidently introduced by careless refactoring in commit f0e44751d. Back-patch accordingly. Discussion: https://postgr.es/m/27543.1528758304@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/cache/relcache.c')
0 files changed, 0 insertions, 0 deletions