aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-03-20 00:58:26 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-03-20 00:58:26 +0000
commitcb8bd60aa488d33cc811495c2692e807f393e6cf (patch)
tree0e7040bd610a79a8933736566d5c591a049b603f /src/backend/access/gist/gistproc.c
parent3f060dfa3b6b729e6a48aef7bdd556738e3a74ce (diff)
downloadpostgresql-cb8bd60aa488d33cc811495c2692e807f393e6cf.tar.gz
postgresql-cb8bd60aa488d33cc811495c2692e807f393e6cf.zip
Clear error_context_stack and debug_query_string at the beginning of proc_exit,
so that we won't try to attach any context printouts to messages that get emitted while exiting. Per report from Dennis Koegel, the context functions won't necessarily work after we've started shutting down the backend, and it seems possible that debug_query_string could be pointing at freed storage as well. The context information doesn't seem particularly relevant to such messages anyway, so there's little lost by suppressing it. Back-patch to all supported branches. I can only demonstrate a crash with log_disconnections messages back to 8.1, but the risk seems real in 8.0 and before anyway.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions