Great TODO updates from Tom:
< Currently SIGTERM of a backend can lead to lock table corruption.
> Lock table corruption following SIGTERM of an individual backend
> has been reported in 8.0. A possible cause was fixed in 8.1, but
> it is unknown whether other problems exist. This item mostly
> requires additional testing rather than of writing any new code.
< o Allow postgresql.conf values to be set so they can not be changed
< by the user
< * %Remove Money type, add money formatting for decimal type
> * Improve the MONEY data type
> Change the MONEY data type to use DECIMAL internally, with special
> locale-aware output formatting.
< o %Allow MIN()/MAX() on arrays
> o -Allow MIN()/MAX() on arrays
< o Modify array literal representation to handle array index lower bound
> o -Modify array literal representation to handle array index lower bound
> o Auto-delete large objects when referencing row is deleted
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> /contrib/lo offers this functionality.
< o Auto-delete large objects when referencing row is deleted
< * %Have views on temporary tables exist in the temporary namespace
< * Allow temporary views on non-temporary tables
< * %Allow RULE recompilation
> * -Have views on temporary tables exist in the temporary namespace
> * -Allow temporary views on non-temporary tables
> * Allow VIEW/RULE recompilation when the underlying tables change
> This is like DELETE CASCADE, but truncates.
< * Make row-wise comparisons work per SQL spec
> * %Make row-wise comparisons work per SQL spec
< o Currently the system uses the operating system COPY command to
< create a new database. Add ON COMMIT capability to CREATE TABLE AS
> o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
< o %Add ALTER DOMAIN TYPE
> o Add ALTER DOMAIN to modify the underlying data type
< o %Disallow dropping of an inherited constraint
< o -Allow objects to be moved to different schemas
> o Add missing object types for ALTER ... SET SCHEMA
< o %Prevent child tables from altering constraints like CHECK that were
< inherited from the parent table
> o %Disallow dropping of an inherited constraint
> o %Prevent child tables from altering or dropping constraints
> like CHECK that were inherited from the parent table
< o Handle references to temporary tables that are created, destroyed,
< then recreated during a session, and EXECUTE is not used
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
< o Add table function support to pltcl, plperl, plpython?
< o Allow PL/pgSQL to name columns by ordinal position, e.g. rec.(3)
> o Add table function support to pltcl, plpython
> o Allow function argument names to be queries from PL/PgSQL
< o Pass arrays natively instead of as text between plperl and postgres
< o Add support for polymorphic arguments and return types to plperl
> o -Pass arrays natively instead of as text between plperl and postgres
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
< * Allow libpq to access SQLSTATE so pg_ctl can test for connection failure
< This would be used for checking if the server is up.
< * Have initdb set DateStyle based on locale?
> * Have initdb set the input DateStyle (MDY or DMY) based on locale?
< * Add a schema option to createlang
< o Add pg_dumpall custom format dumps.
< This is probably best done by combining pg_dump and pg_dumpall
< into a single binary.
> o Add pg_dumpall custom format dumps?
< o Remove unnecessary abstractions in pg_dump source code
> o Remove unnecessary function pointer abstractions in pg_dump source
< * %Remove CREATE CONSTRAINT TRIGGER
< This was used in older releases to dump referential integrity
> This is particularly important for references to temporary tables
> in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
> in PL/PgSQL is to use EXECUTE.
< * Fetch heap pages matching index entries in sequential order
> * -Fetch heap pages matching index entries in sequential order
< Currently no only one hash bucket can be stored on a page. Ideally
> Currently only one hash bucket can be stored on a page. Ideally
> o Add WAL logging for crash recovery
> o Allow multi-column hash indexes
> Ideally this requires a separate test program that can be run
> at initdb time or optionally later.
< * Improve the background writer
> * -Improve the background writer
< For large table adjustements during vacuum, it is faster to reindex
< rather than update the index.
> For large table adjustements during VACUUM FULL, it is faster to
> reindex rather than update the index.
< * Reduce lock time by moving tuples with read lock, then write
< lock and truncate table
> * Reduce lock time during VACUUM FULL by moving tuples with read lock,
> then write lock and truncate table
< o %Suggest VACUUM FULL if a table is nearly empty
> o %Issue log message to suggest VACUUM FULL if a table is nearly
< * Add WAL index reliability improvement to non-btree indexes
< * ANALYZE should record a pg_statistic entry for an all-NULL column
> * -ANALYZE should record a pg_statistic entry for an all-NULL column
> * Allow constraint_elimination to be automatically performed
> This requires additional code to reduce the performance loss caused by
> constraint elimination.
< * Remove memory/file descriptor freeing before ereport(ERROR)
> * %Remove memory/file descriptor freeing before ereport(ERROR)
< * Promote debug_query_string into a server-side function current_query()
< * Allow the identifier length to be increased via a configure option
> * %Promote debug_query_string into a server-side function current_query()
> * %Allow the identifier length to be increased via a configure option
< * Fix cross-compiling of time zone database via 'zic'
< o Improve dlerror() reporting string
> o -Improve dlerror() reporting string
< o Add support for Unicode
> o %Add support for Unicode
TODO (r1.1635 -> r1.1636)
TODO.html (r1.142 -> r1.143)
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2005-08-26 18:59:48|
|Subject: pgsql: Remove completed items: < * -Allow limits on per-db/role |
|Previous:||From: Tom Lane||Date: 2005-08-26 17:40:36|
|Subject: pgsql: The idea of using _strncoll() on Windows doesn't work.|