aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-03-12 23:58:35 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-03-12 23:58:35 +0000
commit1dd56fdae41367ca0fdef5c14849a7e755a8ed32 (patch)
tree418a877474808d5e84d8f2ef07f09852724e9542 /src/backend/access/gist
parentd2ab94dac23bab41d25f7f5c7814d7d3a4d5b1c4 (diff)
downloadpostgresql-1dd56fdae41367ca0fdef5c14849a7e755a8ed32.tar.gz
postgresql-1dd56fdae41367ca0fdef5c14849a7e755a8ed32.zip
Fix pg_plan_queries() to restore the previous setting of ActiveSnapshot
(probably NULL) before exiting. Up to now it's just left the variable as it set it, which means that after we're done processing the current client message, ActiveSnapshot is probably pointing at garbage (because this function is typically run in MessageContext which will get reset). There doesn't seem to have been any code path in which that mattered before 8.3, but now the plancache module might try to use the stale value if the next client message is a Bind for a prepared statement that is in need of replanning. Per report from Alex Hunsaker.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions