Fix free space map to correctly track the total amount of FSM space needed
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 21 Sep 2006 20:31:22 +0000 (20:31 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 21 Sep 2006 20:31:22 +0000 (20:31 +0000)
commit3b6ed87afd9f4c97c8cf52e40f3796069fd74226
treedd994c9f02435cfe60244d9ee80d49b2ed41a3db
parentf52056aaf64ecdb1d746086b72bb4da4d8e31ad7
Fix free space map to correctly track the total amount of FSM space needed
even when a single relation requires more than max_fsm_pages pages.  Also,
make VACUUM emit a warning in this case, since it likely means that VACUUM
FULL or other drastic corrective measure is needed.  Per reports from Jeff
Frost and others of unexpected changes in the claimed max_fsm_pages need.
contrib/pg_freespacemap/README.pg_freespacemap
contrib/pg_freespacemap/pg_freespacemap.c
contrib/pg_freespacemap/pg_freespacemap.sql.in
src/backend/access/gin/ginvacuum.c
src/backend/access/gist/gistvacuum.c
src/backend/access/nbtree/nbtree.c
src/backend/commands/vacuum.c
src/backend/commands/vacuumlazy.c
src/backend/storage/freespace/freespace.c
src/include/storage/freespace.h