Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
pgsql: Move increase FSM warning to after lazy_truncate_heap() because
- From: momjian(at)postgresql(dot)org (Bruce Momjian)
- To: pgsql-committers(at)postgresql(dot)org
- Subject: pgsql: Move increase FSM warning to after lazy_truncate_heap() because
- Date: Wed, 21 Feb 2007 18:15:21 -0400 (AST)
- Message-id: <20070221221521(dot)7E37E9FBC31(at)postgresql(dot)org>
Log Message:
-----------
Move increase FSM warning to after lazy_truncate_heap() because the
function might reduce the number of free pages in the table. Recommend
VACUUM FULL only if 20% free.
Simon Riggs.
Modified Files:
--------------
pgsql/src/backend/commands:
vacuumlazy.c (r1.83 -> r1.84)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.83&r2=1.84)
- Prev by Date: pgsql: btree source code cleanups: I refactored findsplitloc and
- Next by Date: pgsql: Update new optional VACUUM FULL hint for translations, per
- Previous by thread: pgsql: btree source code cleanups: I refactored findsplitloc and
- Next by thread: pgsql: Update new optional VACUUM FULL hint for translations, per
- Indexes: