From 01930cea035d4fd9e490a2d1159b26fbd2f43ef3 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 23 Jun 2008 20:20:54 +0000 Subject: [PATCH] Add TODO: * Consider whether duplicate keys should be sorted by block/offset http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php Create new "Sorting" TODO section. --- doc/TODO | 34 ++++++++++++++++----------- doc/src/FAQ/TODO.html | 54 ++++++++++++++++++++++++------------------- 2 files changed, 50 insertions(+), 38 deletions(-) diff --git a/doc/TODO b/doc/TODO index faaafd5c65..1611c21c2b 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Wed Jun 18 21:15:40 EDT 2008 +Last updated: Mon Jun 23 16:20:35 EDT 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1388,6 +1388,25 @@ Indexes o Allow multi-column hash indexes o -During index creation, pre-sort the tuples to improve build speed +Sorting +======= +* Consider using hash buckets to do DISTINCT, rather than sorting + + This would be beneficial when there are few distinct values. This is + already used by GROUP BY. + +* Consider whether duplicate keys should be sorted by block/offset + + http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php + +* -Avoid tuple some tuple copying in sort routines +* Consider being smarter about memory and external files used during + sorts + + http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php + http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php + +* Consider detoasting keys before sorting Fsync @@ -1711,11 +1730,6 @@ Optimizer / Executor http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php -* Consider using hash buckets to do DISTINCT, rather than sorting - - This would be beneficial when there are few distinct values. This is - already used by GROUP BY. - * Log statements where the optimizer row estimates were dramatically different from the number of rows actually found? * Consider compressed annealing to search for query plans @@ -1865,7 +1879,6 @@ Miscellaneous Performance http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php -* -Avoid tuple some tuple copying in sort routines * SMP scalability improvements http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php @@ -1876,12 +1889,6 @@ Miscellaneous Performance http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php -* Consider being smarter about memory and external files used during - sorts - - http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php - http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php - * Allow one transaction to see tuples using the snapshot of another transaction @@ -1917,7 +1924,6 @@ Source Code http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php -* Consider detoasting keys before sorting * Consider GnuTLS if OpenSSL license becomes a problem http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 825bb88850..844dc553dd 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Wed Jun 18 21:15:40 EDT 2008 +Last updated: Mon Jun 23 16:20:35 EDT 2008

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -1203,7 +1203,24 @@ first. There is also a developer's wiki at

  • Allow multi-column hash indexes
  • -During index creation, pre-sort the tuples to improve build speed
    • -

    Fsync

    +

    Sorting

    + +

    Fsync

    -

    Cache Usage

    +

    Cache Usage

    -

    Vacuum

    +

    Vacuum

    -

    Locking

    +

    Locking

    -

    Startup Time Improvements

    +

    Startup Time Improvements

    -

    Write-Ahead Log

    +

    Write-Ahead Log

    -

    Optimizer / Executor

    +

    Optimizer / Executor

    -

    Background Writer

    +

    Background Writer

    -

    Miscellaneous Performance

    +

    Miscellaneous Performance

    -

    Source Code

    +

    Source Code

    -

    Exotic Features

    +

    Exotic Features

    -

    Features We Do Not Want

    +

    Features We Do Not Want