pgsql: Move increase FSM warning to after lazy_truncate_heap() because - Mailing list pgsql-committers

From momjian@postgresql.org (Bruce Momjian)
Subject pgsql: Move increase FSM warning to after lazy_truncate_heap() because
Date
Msg-id 20070221221521.7E37E9FBC31@postgresql.org
Whole thread Raw
List pgsql-committers
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)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: btree source code cleanups: I refactored findsplitloc and
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update new optional VACUUM FULL hint for translations, per