aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-05-26 18:54:36 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-05-26 18:54:36 +0000
commited91252bc252e926595abf7886a9c2aac0e91801 (patch)
treeb2589177969e9fbc944b24a431ed536460f2393c /src/backend/access/gist/gistvacuum.c
parent888706a883df9003ad7e316f86e574301f218cf0 (diff)
downloadpostgresql-ed91252bc252e926595abf7886a9c2aac0e91801.tar.gz
postgresql-ed91252bc252e926595abf7886a9c2aac0e91801.zip
Fix an old corner-case bug in set_config_option: push_old_value has to be
called before, not after, calling the assign_hook if any. This is because push_old_value might fail (due to palloc out-of-memory), and in that case there would be no stack entry to tell transaction abort to undo the GUC assignment. Of course the actual assignment to the GUC variable hasn't happened yet --- but the assign_hook might have altered subsidiary state. Without a stack entry we won't call it again to make it undo such actions. So this is necessary to make the world safe for assign_hooks with side effects. Per a discussion a couple weeks ago with Magnus. Back-patch to 8.0. 7.x did not have the problem because it did not have allocatable stacks of GUC values.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions