mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Mark TODO item "autovacuum on by default" as completed.

Browse Source
This commit is contained in:
Bruce Momjian 2007-01-17 03:43:49 +00:00
parent 6d660587f6
commit 3026e1765f
2 changed files with 16 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Sat Jan 13 10:13:24 EST 2007 Last updated: Tue Jan 16 22:43:34 EST 2007
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
@ -1074,9 +1074,7 @@ Vacuum
o %Issue log message to suggest VACUUM FULL if a table is nearly o %Issue log message to suggest VACUUM FULL if a table is nearly
empty? empty?
o Consider logging activity either to the logs or a system view o Consider logging activity either to the logs or a system view
o Turn on by default o -Turn on by default
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php
Locking Locking

19
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Sat Jan 13 10:13:24 EST 2007 Last updated: Tue Jan 16 22:43:34 EST 2007
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -315,7 +315,7 @@ first.
</li><li>Add ISO day of week format 'ID' to to_char() where Monday = 1 </li><li>Add ISO day of week format 'ID' to to_char() where Monday = 1
</li><li>Add a field 'isoyear' to extract(), based on the ISO week </li><li>Add a field 'isoyear' to extract(), based on the ISO week
</li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc </li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
</li><li>Allow inlining of set-returning functions </li><li>Implement inlining of set-returning functions defined in SQL
</li><li>Allow SQL-language functions to return results from RETURNING queries </li><li>Allow SQL-language functions to return results from RETURNING queries
</li></ul> </li></ul>
<h1><a name="section_6">Multi-Language Support</a></h1> <h1><a name="section_6">Multi-Language Support</a></h1>
@ -835,6 +835,8 @@ first.
<p> Currently only one hash bucket can be stored on a page. Ideally <p> Currently only one hash bucket can be stored on a page. Ideally
several hash buckets could be stored on a single page and greater several hash buckets could be stored on a single page and greater
granularity used for the hash algorithm. granularity used for the hash algorithm.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a>
</p> </p>
</li><li>Consider sorting hash buckets so entries can be found using a </li><li>Consider sorting hash buckets so entries can be found using a
binary search, rather than a linear scan binary search, rather than a linear scan
@ -873,6 +875,12 @@ first.
get a count directly from a unique index, but for this to be get a count directly from a unique index, but for this to be
faster than a sequential scan it must avoid access to the heap faster than a sequential scan it must avoid access to the heap
to obtain tuple visibility information. to obtain tuple visibility information.
</p>
</li><li>Provide a way to calculate an "estimated COUNT(*)"
<p> Perhaps by using the optimizer's cardinality estimates or random
sampling.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>
</p> </p>
</li><li>Allow data to be pulled directly from indexes </li><li>Allow data to be pulled directly from indexes
<p> Currently indexes do not have enough tuple visibility information <p> Currently indexes do not have enough tuple visibility information
@ -958,15 +966,16 @@ first.
</li><li>%Issue log message to suggest VACUUM FULL if a table is nearly </li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
empty? empty?
</li><li>Consider logging activity either to the logs or a system view </li><li>Consider logging activity either to the logs or a system view
</li><li>Turn on by default </li><li>-<em>Turn on by default</em>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php</a>
</p>
</li></ul> </li></ul>
</li></ul> </li></ul>
<h1><a name="section_16">Locking</a></h1> <h1><a name="section_16">Locking</a></h1>
<ul> <ul>
<li>Fix priority ordering of read and write light-weight locks (Neil) <li>Fix priority ordering of read and write light-weight locks (Neil)
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php</a>
</p>
</li></ul> </li></ul>
<h1><a name="section_17">Startup Time Improvements</a></h1> <h1><a name="section_17">Startup Time Improvements</a></h1>