From 5495575903e35ceb40d32055ab55e9377460208f Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 17 Jun 2005 19:20:27 +0000 Subject: Re-order item. > * Auto-fill the free space map by scanning the buffer cache or by > checking pages written by the background writer < * Auto-fill the free space map by scanning the buffer cache or by < checking pages written by the background writer --- doc/src/FAQ/TODO.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 2595be27184..5dbd90c68ee 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Jun 17 09:47:23 EDT 2005 +Last updated: Fri Jun 17 15:20:21 EDT 2005

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -736,14 +736,14 @@ first.

This allows vacuum to target specific pages for possible free space without requiring a sequential scan.

+
  • Auto-fill the free space map by scanning the buffer cache or by + checking pages written by the background writer
  • 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.

    -
  • Auto-fill the free space map by scanning the buffer cache or by - checking pages written by the background writer
  • Auto-vacuum