summaryrefslogtreecommitdiff
path: root/contrib/pg_freespacemap/pg_freespacemap.sql.in
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-09-21 20:31:22 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-09-21 20:31:22 +0000
commit9e936693a9fc464511b52b14fb681cdea014bf59 (patch)
tree2781b3043a8b46dcf3d40d6410d2b7b970fa0b5e /contrib/pg_freespacemap/pg_freespacemap.sql.in
parentb0d64a090b14217c9bcf620a32c60eab1354470f (diff)
downloadpostgresql-9e936693a9fc464511b52b14fb681cdea014bf59.tar.gz
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.
Diffstat (limited to 'contrib/pg_freespacemap/pg_freespacemap.sql.in')
-rw-r--r--contrib/pg_freespacemap/pg_freespacemap.sql.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/pg_freespacemap/pg_freespacemap.sql.in b/contrib/pg_freespacemap/pg_freespacemap.sql.in
index c45335e3b1..a91a991502 100644
--- a/contrib/pg_freespacemap/pg_freespacemap.sql.in
+++ b/contrib/pg_freespacemap/pg_freespacemap.sql.in
@@ -30,7 +30,7 @@ CREATE VIEW pg_freespacemap_relations AS
reldatabase oid,
relfilenode oid,
avgrequest integer,
- lastpagecount integer,
+ interestingpages integer,
storedpages integer,
nextpage integer);