From 3ca214ed1a1d08b19b4e8b7269050b65e1c2c0f9 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 19 Apr 2008 12:33:06 +0000 Subject: [PATCH] Update TODO using new script. --- doc/TODO | 2 +- doc/src/FAQ/TODO.html | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/TODO b/doc/TODO index 08d85bfa9d..8eacdd6f1f 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat Apr 19 08:15:19 EDT 2008 +Last updated: Sat Apr 19 08:32:51 EDT 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 06aa4e1147..9ceb4ad544 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: Sat Apr 19 08:15:19 EDT 2008 +Last updated: Sat Apr 19 08:32:51 EDT 2008

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

  • Allow function parameters to be passed by name, get_employee_salary(12345 AS emp_id, 2001 AS tax_year) -
  • Allow handling of %TYPE arrays, e.g. tab.col%TYPE[] +
  • Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
  • Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname) @@ -984,7 +984,7 @@ first. There is also a developer's wiki at
  • Use backend PREPARE/EXECUTE facility for ecpg where possible
  • Implement SQLDA
  • Fix nested C comments -
  • %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified +
  • %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified
  • Make SET CONNECTION thread-aware, non-standard?
  • Allow multidimensional arrays
  • Add internationalized message strings @@ -1384,7 +1384,7 @@ first. There is also a developer's wiki at
    might be dropped or truncated during crash recovery

    Allow tables to bypass WAL writes and just fsync() dirty pages on commit. This should be implemented using ALTER TABLE, e.g. ALTER - TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using + TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using non-default logging should not use referential integrity with default-logging tables. A table without dirty buffers during a crash could perhaps avoid the drop/truncate.