aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/explain.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-21 15:03:36 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-21 15:03:36 -0500
commit593a9631a7947ab95903e87e24786d7e469cc988 (patch)
treef210cb800ca699999325aeb2396e0df44f1163f9 /src/backend/commands/explain.c
parent9789c99d01e7e4460b77c29b77d177f86c45a273 (diff)
downloadpostgresql-593a9631a7947ab95903e87e24786d7e469cc988.tar.gz
postgresql-593a9631a7947ab95903e87e24786d7e469cc988.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/explain.c')
0 files changed, 0 insertions, 0 deletions