aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-21 15:03:44 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-21 15:03:44 -0500
commit6182e01f18f71c48915e2aebb20362294de6e677 (patch)
tree0d52f64f18411716f478902d6417e319d9402924 /src/backend/commands
parent3d2aa2c086116fd41dc7f8cff1e3ec9e5d4e2b2c (diff)
downloadpostgresql-6182e01f18f71c48915e2aebb20362294de6e677.tar.gz
postgresql-6182e01f18f71c48915e2aebb20362294de6e677.zip
Don't clear btpo_cycleid during _bt_vacuum_one_page.
When "vacuuming" a single btree page by removing LP_DEAD tuples, we are not actually within a vacuum operation, but rather in an ordinary insertion process that could well be running concurrently with a vacuum. So clearing the cycleid is incorrect, and could cause the concurrent vacuum to miss removing tuples that it needs to remove. This is a longstanding bug introduced by commit e6284649b9e30372b3990107a082bc7520325676 of 2006-07-25. I believe it explains Maxim Boguk's recent report of index corruption, and probably some other previously unexplained reports. In 9.0 and up this is a one-line fix; before that we need to introduce a flag to tell _bt_delitems what to do.
Diffstat (limited to 'src/backend/commands')
0 files changed, 0 insertions, 0 deletions