PostgreSQL TODO List
====================
-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.
-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
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)
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
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
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.