rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update TODO with lost change, mostly completed items and whitespace 

corrections.  Not sure why these were not in CVS.  Researching.
This commit is contained in:
Bruce Momjian 2007-08-28 03:00:36 +00:00
parent 28662b850c
commit 76534c61b3
1 changed files with 48 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/TODO
View File

@ -1,7 +1,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Wed Aug 1 19:13:20 EDT 2007 Last updated: Mon Aug 27 22:56:24 EDT 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.
@ -171,11 +171,7 @@ Administration
Monitoring Monitoring
========== ==========
* Allow server log information to be output as INSERT statements * -Allow server log information to be output as CSV format
This would allow server log information to be easily loaded into
a database for analysis.
* -Add ability to monitor the use of temporary sort files * -Add ability to monitor the use of temporary sort files
@ -1137,6 +1133,13 @@ Cache Usage
accessed bitmaps would have to be stored in shared memory. One 8k accessed bitmaps would have to be stored in shared memory. One 8k
page of bitmaps could track 512MB of heap pages. page of bitmaps could track 512MB of heap pages.
A third idea would be for a heap scan to check if all rows are visible
and if so set a per-table flag which can be checked by index scans.
Any change to the table would have to clear the flag. To detect
changes during the heap scan a counter could be set at the start and
checked at the end --- if it is the same, the table has not been
modified --- any table change would increment the counter.
* Consider automatic caching of statements at various levels: * Consider automatic caching of statements at various levels:
o Parsed query tree o Parsed query tree
@ -1221,6 +1224,11 @@ Vacuum
http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
* Reduce XID consumption of read-only queries
http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php
* Auto-vacuum * Auto-vacuum
o Use free-space map information to guide refilling o Use free-space map information to guide refilling