Skip to content

Commit 3026e17

Browse files
committed
Mark TODO item "autovacuum on by default" as completed.
1 parent 6d66058 commit 3026e17

File tree

2 files changed

+16
-9
lines changed

2 files changed

+16
-9
lines changed

doc/TODO

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer: Bruce Momjian (bruce@momjian.us)
5-
Last updated: Sat Jan 13 10:13:24 EST 2007
5+
Last updated: Tue Jan 16 22:43:34 EST 2007
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1074,9 +1074,7 @@ Vacuum
10741074
o %Issue log message to suggest VACUUM FULL if a table is nearly
10751075
empty?
10761076
o Consider logging activity either to the logs or a system view
1077-
o Turn on by default
1078-
1079-
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php
1077+
o -Turn on by default
10801078

10811079

10821080
Locking

doc/src/FAQ/TODO.html

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
99
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Sat Jan 13 10:13:24 EST 2007
11+
Last updated: Tue Jan 16 22:43:34 EST 2007
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -315,7 +315,7 @@ <h1><a name="section_5">Functions</a></h1>
315315
</li><li>Add ISO day of week format 'ID' to to_char() where Monday = 1
316316
</li><li>Add a field 'isoyear' to extract(), based on the ISO week
317317
</li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
318-
</li><li>Allow inlining of set-returning functions
318+
</li><li>Implement inlining of set-returning functions defined in SQL
319319
</li><li>Allow SQL-language functions to return results from RETURNING queries
320320
</li></ul>
321321
<h1><a name="section_6">Multi-Language Support</a></h1>
@@ -835,6 +835,8 @@ <h1><a name="section_12">Indexes</a></h1>
835835
<p> Currently only one hash bucket can be stored on a page. Ideally
836836
several hash buckets could be stored on a single page and greater
837837
granularity used for the hash algorithm.
838+
</p>
839+
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a>
838840
</p>
839841
</li><li>Consider sorting hash buckets so entries can be found using a
840842
binary search, rather than a linear scan
@@ -873,6 +875,12 @@ <h1><a name="section_14">Cache Usage</a></h1>
873875
get a count directly from a unique index, but for this to be
874876
faster than a sequential scan it must avoid access to the heap
875877
to obtain tuple visibility information.
878+
</p>
879+
</li><li>Provide a way to calculate an "estimated COUNT(*)"
880+
<p> Perhaps by using the optimizer's cardinality estimates or random
881+
sampling.
882+
</p>
883+
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>
876884
</p>
877885
</li><li>Allow data to be pulled directly from indexes
878886
<p> Currently indexes do not have enough tuple visibility information
@@ -958,15 +966,16 @@ <h1><a name="section_15">Vacuum</a></h1>
958966
</li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
959967
empty?
960968
</li><li>Consider logging activity either to the logs or a system view
961-
</li><li>Turn on by default
962-
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php</a>
963-
</p>
969+
</li><li>-<em>Turn on by default</em>
964970
</li></ul>
965971
</li></ul>
966972
<h1><a name="section_16">Locking</a></h1>
967973

968974
<ul>
969975
<li>Fix priority ordering of read and write light-weight locks (Neil)
976+
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php</a>
977+
<a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php</a>
978+
</p>
970979
</li></ul>
971980
<h1><a name="section_17">Startup Time Improvements</a></h1>
972981

0 commit comments

Comments
 (0)