aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-06-17 19:20:27 +0000
committerBruce Momjian <bruce@momjian.us>2005-06-17 19:20:27 +0000
commit5495575903e35ceb40d32055ab55e9377460208f (patch)
treeda89ec6ae2dc17fc863db8f32395a0567080f4ac
parent524ec00d3e3f7cff97e30e7b67c597f2e8ddbcf0 (diff)
downloadpostgresql-5495575903e35ceb40d32055ab55e9377460208f.tar.gz
postgresql-5495575903e35ceb40d32055ab55e9377460208f.zip
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
-rw-r--r--doc/TODO6
-rw-r--r--doc/src/FAQ/TODO.html6
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/TODO b/doc/TODO
index 1db986125a8..be52d09d1ee 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,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.
@@ -800,6 +800,8 @@ Vacuum
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
@@ -807,8 +809,6 @@ Vacuum
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
o Move into the backend code
o Use free-space map information to guide refilling
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 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Fri Jun 17 09:47:23 EDT 2005
+Last updated: Fri Jun 17 15:20:21 EDT 2005
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -736,14 +736,14 @@ first.
<p> This allows vacuum to target specific pages for possible free space
without requiring a sequential scan.
</p>
+ </li><li>Auto-fill the free space map by scanning the buffer cache or by
+ checking pages written by the background writer
</li><li>Create a bitmap of pages that need vacuuming
<p> 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.
</p>
- </li><li>Auto-fill the free space map by scanning the buffer cache or by
- checking pages written by the background writer
</li><li>Auto-vacuum
<ul>
<li>Move into the backend code