Log Message:
-----------
Rearrange lazy-vacuum code a little bit to reduce the window between
truncating the table and transaction commit.  This isn't really making
it safe, but at least there is no good reason to do free space map
cleanup within the risk window.  Don't lock out cancel interrupts
until we have to, either.

Modified Files:
--------------
    pgsql/src/backend/commands:
        vacuumlazy.c (r1.129 -> r1.130)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c?r1=1.129&r2=1.130)

pgsql-committers by date

Next:	From: Tom Lane	Date: 2010-02-09 00:28:57
	Subject: pgsql: Allow free space map vacuuming to be interrupted.
Previous:	From: Tom Lane	Date: 2010-02-08 20:39:52
	Subject: pgsql: Create an official API function for C functions to use to check