Re: Autovacuum in the backend

> Added to TODO:
> 
>  * Create a bitmap of pages that need vacuuming
>  
>    Instead of sequentially scanning the entire table, have the background
>    writer or some other process record pages that have expired rows, then
>    VACUUM can look at just those pages rather than the entire table.  In
>    the event of a system crash, the bitmap would probably be invalidated.
> 
Further to this, is there any use case for allowing FSM, or this DSM to spill to disk
if the space fills up.  It would allow the possibility of unusual changes to the db
to not loose space.  You could just load part of the overflow from the disk back
int the FSM in memory and continue using free space.

Regards

Russell Smith