From a3faf37f49025a0a4f5dc31479c54e6b84dab07a Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Tue, 19 Aug 2008 03:08:56 +0000 Subject: Fix some issues that prevent this file to be processed by scripts. While at it, mark a couple of items completed in 8.4: ! o -Prevent long-lived temporary tables from causing frozen-xid advancement starvation ! * -Improve performance of shared invalidation queue for multiple CPUs Also remove a couple of obsolete assignments. --- doc/src/FAQ/TODO.html | 192 ++++++++++++++++++++++++-------------------------- 1 file changed, 92 insertions(+), 100 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 1dc4fe012b0..b79f46d1baa 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -1,9 +1,9 @@ - - + + PostgreSQL TODO List - +

PostgreSQL TODO List

@@ -286,94 +286,92 @@ first. There is also a developer's wiki at
LC_MESSAGES

http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php

Add ISO INTERVAL handling

- -

http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
- http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php +

Add ISO INTERVAL handling +

http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php + http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php

Support ISO INTERVAL syntax if units cannot be determined from - the string, and are supplied after the string -
The SQL standard states that the units after the string - specify the units of the string, e.g. INTERVAL '2' MINUTE - should return '00:02:00'. The current behavior has the units - restrict the interval value to the specified unit or unit - range, INTERVAL '70' SECOND returns '00:00:10'. -
-
For syntax that isn't uniquely ISO or PG syntax, like '1' or - '1:30', treat as ISO if there is a range specification clause, - and as PG if there no clause is present, e.g. interpret '1:30' - MINUTE TO SECOND as '1 minute 30 seconds', and interpret - '1:30' as '1 hour, 30 minutes'. -
-
This makes common cases like SELECT INTERVAL '1' MONTH - SQL-standard results. The SQL standard supports a limited - number of unit combinations and doesn't support unit names in - the string. The PostgreSQL syntax is more flexible in the - range of units supported, e.g. PostgreSQL supports '1 year 1 - hour', while the SQL standard does not. -
-
Add support for year-month syntax, INTERVAL '50-6' YEAR - TO MONTH -
Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 - year' AS INTERVAL MONTH), and this should return '12 months' -
Round or truncate values to the requested precision, e.g. - INTERVAL '11 months' AS YEAR should return one or zero -
Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
- Arrays -
  - Delay resolution of array expression's data type so assignment +
  - Support ISO INTERVAL syntax if units cannot be determined from + the string, and are supplied after the string +
    The SQL standard states that the units after the string + specify the units of the string, e.g. INTERVAL '2' MINUTE + should return '00:02:00'. The current behavior has the units + restrict the interval value to the specified unit or unit + range, INTERVAL '70' SECOND returns '00:00:10'. +
    +
    For syntax that isn't uniquely ISO or PG syntax, like '1' or + '1:30', treat as ISO if there is a range specification clause, + and as PG if there no clause is present, e.g. interpret '1:30' + MINUTE TO SECOND as '1 minute 30 seconds', and interpret + '1:30' as '1 hour, 30 minutes'. +
    +
    This makes common cases like SELECT INTERVAL '1' MONTH + SQL-standard results. The SQL standard supports a limited + number of unit combinations and doesn't support unit names in + the string. The PostgreSQL syntax is more flexible in the + range of units supported, e.g. PostgreSQL supports '1 year 1 + hour', while the SQL standard does not. +
    +
  - Add support for year-month syntax, INTERVAL '50-6' YEAR + TO MONTH +
  - Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 + year' AS INTERVAL MONTH), and this should return '12 months' +
  - Round or truncate values to the requested precision, e.g. + INTERVAL '11 months' AS YEAR should return one or zero +
  - Support precision, CREATE TABLE foo (a INTERVAL MONTH(3)) +
  +
- Arrays +
  - Delay resolution of array expression's data type so assignment coercion can be performed on empty array expressions -
  - Add support for arrays of domains +
  - Add support for arrays of domains
    http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php
    -
  - Allow single-byte header storage for array elements -
  -
- Binary Data -
  - Improve vacuum of large objects, like contrib/vacuumlo? -
  - Add security checking for large objects -
  - Auto-delete large objects when referencing row is deleted +
  - Allow single-byte header storage for array elements +
  +
- Binary Data +
  - Improve vacuum of large objects, like contrib/vacuumlo? +
  - Add security checking for large objects +
  - Auto-delete large objects when referencing row is deleted
    contrib/lo offers this functionality.
    -
  - Allow read/write into TOAST values like large objects +
  - Allow read/write into TOAST values like large objects
    This requires the TOAST column to be stored EXTERNAL.
    -
  - Add API for 64-bit large object access +
  - Add API for 64-bit large object access
    http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
    -
  -
- MONEY data type -
  - Add locale-aware MONEY type, and support multiple currencies +
  +
- MONEY data type +
  - Add locale-aware MONEY type, and support multiple currencies
    http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
    -
  - MONEY dumps in a locale-specific format making it difficult to +
  - MONEY dumps in a locale-specific format making it difficult to restore to a system with a different locale -
  - Allow MONEY to be easily cast to/from other numeric data types -
  -
- Text Search -
  - Allow dictionaries to change the token that is passed on to +
  - Allow MONEY to be easily cast to/from other numeric data types +
  +
- Text Search +
  - Allow dictionaries to change the token that is passed on to later dictionaries
    http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php
    -
  - Consider a function-based API for '@@' searches +
  - Consider a function-based API for '@@' searches
    http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php
    -
  - Improve text search error messages +
  - Improve text search error messages
    http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php
    -
  - Consider changing error to warning for strings larger than one +
  - Consider changing error to warning for strings larger than one megabyte
    http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php http://archives.postgresql.org/pgsql-patches/2008-03/msg00062.php
    -

Functions

@@ -431,7 +429,7 @@ first. There is also a developer's wiki at

Prevent malicious functions from being executed with the permissions of unsuspecting users -

Index functions are safe, so VACUUM and ANALYZE are safe too. +

Index functions are safe, so VACUUM and ANALYZE are safe too. Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable. http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php

@@ -493,7 +491,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00767.php http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php - http://wiki.postgresql.org/wiki/Todo:Collate + http://wiki.postgresql.org/wiki/Todo:Collate http://wiki.postgresql.org/wiki/Todo:ICU

Support multiple simultaneous character sets, per SQL92 @@ -578,7 +576,7 @@ first. There is also a developer's wiki at

Improve failure message when DROP DATABASE is used on a database that has prepared transactions

Allow prepared transactions with temporary tables created and dropped - in the same transaction, and when an ON COMMIT DELETE ROWS temporary + in the same transaction, and when an ON COMMIT DELETE ROWS temporary table is accessed

http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php

@@ -788,12 +786,10 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php

Allow COPY to report errors sooner -

- -

http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php +

http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php

GRANT/REVOKE +

GRANT/REVOKE

Allow column-level privileges
%Allow GRANT/REVOKE permissions to be applied to all schema objects @@ -825,7 +821,7 @@ first. There is also a developer's wiki at
LISTEN/NOTIFY
- Allow LISTEN/NOTIFY to store info in memory rather than tables? -
  Currently LISTEN/NOTIFY information is stored in pg_listener. +
  Currently LISTEN/NOTIFY information is stored in pg_listener. Storing such information in memory would improve performance.
- Add optional textual message to NOTIFY @@ -1000,7 +996,7 @@ first. There is also a developer's wiki at
  widths. Perhaps the word wrapping could use the same algorithm documented in the W3C specification. http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php - http://www.w3.org/TR/CSS21/tables.htmlauto-table-layout + http://www.w3.org/TR/CSS21/tables.html#auto-table-layout
- Add "auto" expanded mode that outputs in expanded format if "wrapped" mode can't wrap the output to the screen width
  http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php @@ -1106,8 +1102,8 @@ first. There is also a developer's wiki at

Triggers

- +

Triggers

Add deferred trigger queue file
Right now all deferred trigger information is stored in backend @@ -1239,24 +1235,23 @@ first. There is also a developer's wiki at
digital trees (see Aoki)

Hash -

http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php -

Pack hash index buckets onto disk pages more efficiently +
- http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php +
- Pack hash index buckets onto disk pages more efficiently
  Currently only one hash bucket can be stored on a page. Ideally several hash buckets could be stored on a single page and greater granularity used for the hash algorithm.
  
  http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php
  -
- Consider sorting hash buckets so entries can be found using a +
- Consider sorting hash buckets so entries can be found using a binary search, rather than a linear scan -
- In hash indexes, consider storing the hash value with or instead +
- In hash indexes, consider storing the hash value with or instead of the key itself -
- Add WAL logging for crash recovery -
- Allow multi-column hash indexes -
- -During index creation, pre-sort the tuples to improve build speed +
- Add WAL logging for crash recovery +
- Allow multi-column hash indexes +
- -During index creation, pre-sort the tuples to improve build speed +

Sorting

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. + 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 @@ -1331,12 +1326,9 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php

Consider automatic caching of statements at various levels: -
- Parsed query tree -
- Query execute plan -
- Query results - http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php -
+ Parsed query tree, query execution plan, query results +
http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php +
Consider increasing internal areas when shared buffers is increased
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
@@ -1401,7 +1393,7 @@ first. There is also a developer's wiki at
Improve control of auto-vacuum
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
-
Prevent long-lived temporary tables from causing frozen-xid +
-Prevent long-lived temporary tables from causing frozen-xid advancement starvation
The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can do that. @@ -1420,7 +1412,7 @@ first. There is also a developer's wiki at

Locking
- Fix priority ordering of read and write light-weight locks (Neil) +
- Fix priority ordering of read and write light-weight locks
  http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php
  @@ -1575,7 +1567,7 @@ first. There is also a developer's wiki at
  catalogs and the transaction status log.
- Consider adding buffers the background writer finds reusable to the - free list + free list
  http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
- Automatically tune bgwriter_delay based on activity rather then using a @@ -1661,7 +1653,7 @@ first. There is also a developer's wiki at
  AcceptInvalidationMessages() call
  http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php
  -
- Improve performance of shared invalidation queue for multiple CPUs +
- -Improve performance of shared invalidation queue for multiple CPUs
  http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
- Consider Cartesian joins when both relations are needed to form an @@ -1702,7 +1694,7 @@ first. There is also a developer's wiki at
- %Remove warnings created by -Wcast-align
- Move platform-specific ps status display info from ps_status.c to ports
- Add optional CRC checksum to heap and index pages -
- Improve documentation to build only interfaces (Marc) +
- Improve documentation to build only interfaces
- Remove or relicense modules that are not under the BSD license, if possible
- Acquire lock on a relation before building a relcache entry for it
- Allow cross-compiling by generating the zic database on the target system @@ -1830,7 +1822,7 @@ first. There is also a developer's wiki at
  modification.
- Allow plug-in modules to emulate features from other databases -
- Add features of Oracle-style packages (Pavel) +
- Add features of Oracle-style packages
  A package would be a schema with session-local variables, public/private functions, and initialization functions. It is also possible to implement these capabilities @@ -1850,7 +1842,7 @@ first. There is also a developer's wiki at
  
  http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
-
Features We Do Not Want
+
Features We Do _Not_ Want
- All backends running as threads in a single process (not wanted) -- cgit v1.2.3