pgsql: Fix free space map to correctly track the total amount of FSM

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix free space map to correctly track the total amount of FSM
Date: 2006-09-21 20:31:22
Message-ID: 20060921203123.0031B9FB2F6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Log Message:
-----------
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.

Modified Files:
--------------
pgsql/contrib/pg_freespacemap:
README.pg_freespacemap (r1.4 -> r1.5)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/README.pg_freespacemap.diff?r1=1.4&r2=1.5)
pg_freespacemap.c (r1.6 -> r1.7)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.c.diff?r1=1.6&r2=1.7)
pg_freespacemap.sql.in (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_freespacemap/pg_freespacemap.sql.in.diff?r1=1.5&r2=1.6)
pgsql/src/backend/access/gin:
ginvacuum.c (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginvacuum.c.diff?r1=1.5&r2=1.6)
pgsql/src/backend/access/gist:
gistvacuum.c (r1.26 -> r1.27)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistvacuum.c.diff?r1=1.26&r2=1.27)
pgsql/src/backend/access/nbtree:
nbtree.c (r1.150 -> r1.151)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.150&r2=1.151)
pgsql/src/backend/commands:
vacuum.c (r1.339 -> r1.340)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.339&r2=1.340)
vacuumlazy.c (r1.78 -> r1.79)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.78&r2=1.79)
pgsql/src/backend/storage/freespace:
freespace.c (r1.54 -> r1.55)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/freespace.c.diff?r1=1.54&r2=1.55)
pgsql/src/include/storage:
freespace.h (r1.21 -> r1.22)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/freespace.h.diff?r1=1.21&r2=1.22)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message User Knt 2006-09-21 22:05:48 plscheme - plscheme: Fixed printing stuff in exception handler and added
Previous Message User Mario__ 2006-09-21 18:07:17 webtranslator - l10n: in the front-end '<', '/>', '\n' were changed by

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2006-09-21 20:37:26 Re: pg_upgrade: downgradebility
Previous Message Kevin Brown 2006-09-21 20:20:43 Re: Cause of moving-target FSM space-needed reports