1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgres/doc/src/FAQ/TODO.html

1690 lines
101 KiB
HTML
Raw Normal View History

Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-30 19:07:20 +00:00
<title>PostgreSQL TODO List</title>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<meta name="generator" content="HTML::TextToHTML v2.25"/>
</head>
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-30 19:07:20 +00:00
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Add to TODO: > > o Fix port/rint.c to be spec-compliant > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php
2008-03-25 02:23:43 +00:00
Last updated: Mon Mar 24 22:23:38 EDT 2008
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-30 19:07:20 +00:00
</p>
Update URL for TODO list.
2005-04-22 13:38:19 +00:00
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Dashed items are now for 8.3: < #A hyphen, "-", marks changes that will appear in the upcoming 8.2 release.# > #A hyphen, "-", marks changes that will appear in the upcoming 8.3 release.#
2006-09-19 19:20:21 +00:00
<p><strong>A hyphen, "-", marks changes that will appear in the upcoming 8.3 release.</strong><br/>
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
<strong>A percent sign, "%", marks items that are easier to implement.</strong>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
<p>Bracketed items, "[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]", have more detail.
</p>
<p>This list contains all known PostgreSQL bugs and feature requests. If<br/>
you would like to work on an item, please read the Developer's FAQ<br/>
Add wiki URL: < first. > first. There is also a developer's wiki at > http://developer.postgresql.org.
2007-01-20 02:18:37 +00:00
first. There is also a developer's wiki at<br/>
<a href="http://developer.postgresql.org">http://developer.postgresql.org</a>.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-30 19:07:20 +00:00
<h1><a name="section_2">Administration</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
<li>Allow administrators to safely terminate individual sessions either
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
via an SQL function or SIGTERM
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
<p> 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.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a>
Add URL for: * Allow administrators to safely terminate individual sessions either via an SQL function or SIGTERM > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
2008-03-11 14:25:51 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php</a>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</p>
</li><li>Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php</a>
Add desciption for terminate: > > Currently SIGTERM of a backend can lead to lock table corruption. >
2005-06-24 21:28:30 +00:00
</p>
Not easy, per Alvaro: < * %Set proper permissions on non-system schemas during db creation > * Set proper permissions on non-system schemas during db creation
2007-04-17 20:47:55 +00:00
</li><li>Set proper permissions on non-system schemas during db creation
Add warning about TODO item: < Currently all schemas are owned by the super-user because they are < copied from the template1 database. > Currently all schemas are owned by the super-user because they are copied > from the template1 database. However, since all objects are inherited > from the template database, it is not clear that setting schemas to the db > owner is correct.
2007-04-17 20:50:34 +00:00
<p> Currently all schemas are owned by the super-user because they are copied
from the template1 database. However, since all objects are inherited
from the template database, it is not clear that setting schemas to the db
owner is correct.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add: > * Add function to report the time of the most recent server reload
2005-09-23 03:06:03 +00:00
</li><li>Add function to report the time of the most recent server reload
Add: > * Allow statistics collector information to be pulled from the collector > process directly, rather than requiring the collector to write a > filesystem file twice a second?
2006-02-01 17:32:45 +00:00
</li><li>Allow statistics collector information to be pulled from the collector
process directly, rather than requiring the collector to write a
filesystem file twice a second?
Add to TODO: > * Reduce file system activity overhead of statistics file pgstat.stat > > http://archives.postgresql.org/pgsql-general/2007-12/msg00106.php >
2008-03-17 23:32:21 +00:00
</li><li>Reduce file system activity overhead of statistics file pgstat.stat
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-12/msg00106.php">http://archives.postgresql.org/pgsql-general/2007-12/msg00106.php</a>
</p>
Add: > * Allow statistics last vacuum/analyze execution times to be displayed > without requiring stats_row_level to be enabled
2008-03-11 15:52:02 +00:00
</li><li>Allow statistics last vacuum/analyze execution times to be displayed
without requiring stats_row_level to be enabled
Add URL: * Allow statistics last vacuum/analyze execution times to be displayed without requiring stats_row_level to be enabled > > http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php >
2008-03-24 16:11:27 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php">http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php</a>
</p>
Add: > * Allow log_min_messages to be specified on a per-module basis > > This would allow administrators to see more detailed information from > specific sections of the backend, e.g. checkpoints, autovacuum, etc.
2006-04-10 21:06:23 +00:00
</li><li>Allow log_min_messages to be specified on a per-module basis
<p> This would allow administrators to see more detailed information from
specific sections of the backend, e.g. checkpoints, autovacuum, etc.
Add to item log_min_error_messages item: > Another idea is to allow separate configuration files for each module, > or allow arbitrary SET commands to be passed to them.
2006-04-27 15:56:17 +00:00
Another idea is to allow separate configuration files for each module,
or allow arbitrary SET commands to be passed to them.
Add: > * Allow log_min_messages to be specified on a per-module basis > > This would allow administrators to see more detailed information from > specific sections of the backend, e.g. checkpoints, autovacuum, etc.
2006-04-10 21:06:23 +00:00
</p>
Add: > * Simplify ability to create partitioned tables > > This would allow creation of partitioned tables without requiring > creation of rules for INSERT/UPDATE/DELETE, and constraints for > rapid partition selection. Options could include range and hash > partition selection. > > * Allow auto-selection of partitioned tables for min/max() operations
2006-09-02 23:47:39 +00:00
</li><li>Simplify ability to create partitioned tables
<p> This would allow creation of partitioned tables without requiring
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints
for rapid partition selection. Options could include range and hash
Add: > * Simplify ability to create partitioned tables > > This would allow creation of partitioned tables without requiring > creation of rules for INSERT/UPDATE/DELETE, and constraints for > rapid partition selection. Options could include range and hash > partition selection. > > * Allow auto-selection of partitioned tables for min/max() operations
2006-09-02 23:47:39 +00:00
partition selection.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php</a>
Add URL for: * Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php
2007-04-09 21:18:29 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php</a>
Add URLs for: * Simplify ability to create partitioned tables This would allow creation of partitioned tables without requiring creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection. Options could include range and hash partition selection. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php
2008-03-22 01:30:21 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php</a>
Add URL for: * Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php
2008-03-22 01:46:30 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php</a>
Add URL for: * Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php
2008-03-22 01:47:38 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php</a>
Add URLs for: * Simplify ability to create partitioned tables This would allow creation of partitioned tables without requiring creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection. Options could include range and hash partition selection. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php
2008-03-22 01:30:21 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php</a>
Add: > * Simplify ability to create partitioned tables > > This would allow creation of partitioned tables without requiring > creation of rules for INSERT/UPDATE/DELETE, and constraints for > rapid partition selection. Options could include range and hash > partition selection. > > * Allow auto-selection of partitioned tables for min/max() operations
2006-09-02 23:47:39 +00:00
</p>
</li><li>Allow auto-selection of partitioned tables for min/max() operations
Add: > * Allow more complex user/database default GUC settings > Currently, ALTER USER and ALTER DATABASE support per-user and > per-database defaults. Consider adding per-user-and-database > defaults so things like search_path can be defaulted for a > specific user connecting to a specific database. > >
2006-09-30 03:55:32 +00:00
</li><li>Allow more complex user/database default GUC settings
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently ALTER USER and ALTER DATABASE support per-user and
Add: > * Allow more complex user/database default GUC settings > Currently, ALTER USER and ALTER DATABASE support per-user and > per-database defaults. Consider adding per-user-and-database > defaults so things like search_path can be defaulted for a > specific user connecting to a specific database. > >
2006-09-30 03:55:32 +00:00
per-database defaults. Consider adding per-user-and-database
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
defaults so things like search_path can be defaulted for a
Add: > * Allow more complex user/database default GUC settings > Currently, ALTER USER and ALTER DATABASE support per-user and > per-database defaults. Consider adding per-user-and-database > defaults so things like search_path can be defaulted for a > specific user connecting to a specific database. > >
2006-09-30 03:55:32 +00:00
specific user connecting to a specific database.
Add: > > * Allow custom variable classes that can restrict who can set the values > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php >
2007-02-04 04:06:08 +00:00
</p>
</li><li>Allow custom variable classes that can restrict who can set the values
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php</a>
Add: > * Allow more complex user/database default GUC settings > Currently, ALTER USER and ALTER DATABASE support per-user and > per-database defaults. Consider adding per-user-and-database > defaults so things like search_path can be defaulted for a > specific user connecting to a specific database. > >
2006-09-30 03:55:32 +00:00
</p>
Add, per Alvaro: > > * Implement the SQL standard mechanism whereby REVOKE ROLE revokes only > the privilege granted by the invoking role, and not those granted > by other roles
2007-05-17 22:44:11 +00:00
</li><li>Implement the SQL standard mechanism whereby REVOKE ROLE revokes only
the privilege granted by the invoking role, and not those granted
by other roles
Add URL for: * Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles > > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php
2007-05-17 22:53:23 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php">http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php</a>
Add: > > * Allow SSL authentication/encryption over unix domain sockets > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php
2007-12-30 00:42:38 +00:00
</p>
</li><li>Allow SSL authentication/encryption over unix domain sockets
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php</a>
Add to TODO: > > * Allow SSL key file permission checks to be optionally disabled when > sharing SSL keys with other applications > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php
2008-03-17 23:56:30 +00:00
</p>
</li><li>Allow SSL key file permission checks to be optionally disabled when
sharing SSL keys with other applications
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php">http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php</a>
Add: > > * Allow client certificate names to be checked against the client > hostname > > This is already implemented in > libpq/fe-secure.c::verify_peer_name_matches_certificate() but the code > is commented out.
2008-03-06 21:25:50 +00:00
</p>
</li><li>Allow client certificate names to be checked against the client
hostname
<p> This is already implemented in
libpq/fe-secure.c::verify_peer_name_matches_certificate() but the code
is commented out.
Add URL for: * Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles > > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php
2007-05-17 22:53:23 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Configuration files
<ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<li>Allow pg_hba.conf to specify host names along with IP addresses
Add: > > o Allow pg_hba.conf to specify host names along with IP addresses > > Host name lookup could occur when the postmaster reads the > pg_hba.conf file, or when the backend starts. Another > solution would be to reverse lookup the connection IP and > check that hostname against the host names in pg_hba.conf. > We could also then check that the host name maps to the IP > address.
2006-02-13 03:55:02 +00:00
<p> Host name lookup could occur when the postmaster reads the
pg_hba.conf file, or when the backend starts. Another
solution would be to reverse lookup the connection IP and
check that hostname against the host names in pg_hba.conf.
We could also then check that the host name maps to the IP
address.
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</p>
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Allow postgresql.conf file values to be changed via an SQL
Suggest syntax: < o Allow postgresql.conf file values to be changed via an SQL API > o Allow postgresql.conf file values to be changed via an SQL > API, perhaps using SET GLOBAL
2005-07-31 13:54:52 +00:00
API, perhaps using SET GLOBAL
Add: > o Allow postgresql.conf file values to be changed via an SQL API > o Allow the server to be stopped/restarted via an SQL API
2005-07-25 15:27:06 +00:00
</li><li>Allow the server to be stopped/restarted via an SQL API
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
</li><li>Issue a warning if a change-on-restart-only postgresql.conf value
Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > 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. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
2006-02-07 02:08:08 +00:00
is modified and the server config files are reloaded
Add: > o Consider normalizing fractions in postgresql.conf, perhaps > using '%' > > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php
2008-03-11 20:16:40 +00:00
</li><li>Consider normalizing fractions in postgresql.conf, perhaps
using '%'
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php</a>
Add: > > o Allow Kerberos to disable stripping of realms so we can > check the username@realm against multiple realms > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00009.php
2008-03-17 18:22:44 +00:00
</p>
</li><li>Allow Kerberos to disable stripping of realms so we can
check the username@realm against multiple realms
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00009.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00009.php</a>
Add: > o Consider normalizing fractions in postgresql.conf, perhaps > using '%' > > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php
2008-03-11 20:16:40 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
</li><li>Tablespaces
<ul>
<li>Allow a database in tablespace t1 with tables created in
tablespace t2 to be used as a template for a new database created
with default tablespace t2
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
<p> Currently all objects in the default database tablespace must
have default tablespace specifications. This is because new
databases are created by copying directories. If you mix default
tablespace tables and tablespace-specified tables in the same
directory, creating a new database from such a mixed directory
would create a new database with tables that had incorrect
explicit tablespaces. To fix this would require modifying
pg_class in the newly copied database, which we don't currently
do.
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</p>
</li><li>Allow reporting of which objects are in which tablespaces
<p> This item is difficult because a tablespace can contain objects
from multiple databases. There is a server-side function that
returns the databases which use a specific tablespace, so this
requires a tool that will call that function and connect to each
database to find the objects in each database for that tablespace.
</p>
Cleanups: < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table?
2006-06-09 18:41:57 +00:00
</li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
structure on the recovery computer is different from the original
Cleanups: < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table?
2006-06-09 18:41:57 +00:00
</li><li>Allow per-tablespace quotas
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>Point-In-Time Recovery (PITR)
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
<ul>
Done: < o Add command to archive partially filled write-ahead logs? [pitr] < < Currently only full WAL files are archived. This means that the < most recent transactions aren't available for recovery in case < of a disk failure. < Reorder: < o %Create dump tool for write-ahead logs for use in determining < transaction id for point-in-time recovery > o %Create dump tool for write-ahead logs for use in determining > transaction id for point-in-time recovery
2006-09-26 11:18:29 +00:00
<li>Allow a warm standby system to also allow read-only statements
Adjust TODO spacing.
2008-03-17 21:45:14 +00:00
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php</a>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</p>
Done: < o Add command to archive partially filled write-ahead logs? [pitr] < < Currently only full WAL files are archived. This means that the < most recent transactions aren't available for recovery in case < of a disk failure. < Reorder: < o %Create dump tool for write-ahead logs for use in determining < transaction id for point-in-time recovery > o %Create dump tool for write-ahead logs for use in determining > transaction id for point-in-time recovery
2006-09-26 11:18:29 +00:00
</li><li>%Create dump tool for write-ahead logs for use in determining
Adjust TODO spacing.
2008-03-17 21:45:14 +00:00
transaction id for point-in-time recovery
<p> This is useful for checking PITR recovery.
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</p>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Allow recovery.conf to support the same syntax as
Adjust TODO spacing.
2008-03-17 21:45:14 +00:00
postgresql.conf, including quoting
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php</a>
Add TODO: > > o Fix server restart problem when the server was shutdown during > a PITR backup > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php >
2008-03-17 21:49:11 +00:00
</p>
</li><li>Fix server restart problem when the server was shutdown during
a PITR backup
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php</a>
Add TODO: > o Recreate pg_xlog/archive_status/ if it doesn't exist after > restoring from a PITR backup > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php
2008-03-18 02:37:05 +00:00
</p>
</li><li>Recreate pg_xlog/archive_status/ if it doesn't exist after
restoring from a PITR backup
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php</a>
Add: > o Allow recovery.conf to allow the same syntax as > postgresql.conf, including quoting > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
2007-02-03 22:32:49 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
</li></ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<h1><a name="section_3">Data Types</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Add: < * -Make 64-bit version of the 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 < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the 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 > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
2007-11-26 23:31:09 +00:00
<li>Change NUMERIC to enforce the maximum precision
Add: > * Reduce storage space for small NUMERICs > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php >
2007-03-29 21:43:34 +00:00
</li><li>Reduce storage space for small NUMERICs
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php</a>
Add to: * Reduce storage space for small NUMERICs > http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php
2007-03-29 21:44:39 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php">http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php</a>
Add URL for: * Reduce storage space for small NUMERICs > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php
2008-03-11 20:28:13 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php</a>
Add: > * Reduce storage space for small NUMERICs > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php >
2007-03-29 21:43:34 +00:00
</p>
Remove TODO item, not wanted: < * Add NUMERIC division operator that doesn't round? < < Currently NUMERIC _rounds_ the result to the specified precision. < This means division can return a result that multiplied by the < divisor is greater than the dividend, e.g. this returns a value > 10: < < SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6; < < The positive modulus result returned by NUMERICs might be considered < inaccurate, in one sense. <
2007-03-21 21:21:21 +00:00
</li><li>Fix data types where equality comparison isn't intuitive, e.g. box
> > * Add support for public SYNONYMS > > http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
2006-06-16 18:32:07 +00:00
</li><li>Add support for public SYNONYMs
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php</a>
Add: > > * Fix CREATE CAST on DOMAINs > > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php
2006-06-16 22:05:01 +00:00
</p>
</li><li>Fix CREATE CAST on DOMAINs
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php">http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php</a>
Add URL for domain casting: > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php
2006-09-20 23:01:55 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php</a>
Add: > > * Allow domains to be cast > > http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php
2008-03-12 01:40:09 +00:00
</p>
</li><li>Allow domains to be cast
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php">http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php</a>
Add URL for UUID: > > http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php >
2006-09-18 16:22:32 +00:00
</p>
Add: > * Add support for SQL-standard GENERATED/IDENTITY columns > > http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
2006-07-29 15:56:32 +00:00
</li><li>Add support for SQL-standard GENERATED/IDENTITY columns
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php">http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php</a>
Add URL for: * Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
2007-02-08 21:51:50 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php</a>
Add URLs for: * Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php > http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
2007-05-15 02:36:43 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php">http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php</a>
Add URL for: * Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php
2008-03-05 16:07:21 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php</a>
Add: > * Support a data type with specific enumerated values (ENUM) > > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
2006-08-17 06:45:12 +00:00
</p>
Add XML item. > > * Improve XML support > > http://developer.postgresql.org/index.php/XML_Support
2006-09-14 18:10:38 +00:00
</li><li>Improve XML support
<p> <a href="http://developer.postgresql.org/index.php/XML_Support">http://developer.postgresql.org/index.php/XML_Support</a>
Add: > * Add support for SQL-standard GENERATED/IDENTITY columns > > http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
2006-07-29 15:56:32 +00:00
</p>
Update: < * Consider placing all sequences in a single table > * Consider placing all sequences in a single table, or create a system > view
2007-02-09 01:29:48 +00:00
</li><li>Consider placing all sequences in a single table, or create a system
view
Add URL's for sequence discussions: > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > < o %Have ALTER TABLE RENAME rename SERIAL sequence names > o Have ALTER TABLE RENAME rename SERIAL sequence names > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
2008-03-03 15:06:55 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php">http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php</a>
Add: > > * Allow the UUID type to accept non-standard formats > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php
2008-03-03 19:03:44 +00:00
</p>
</li><li>Allow the UUID type to accept non-standard formats
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php</a>
Added to TODO: > > * Allow text search dictionary to filter out only stop words > > http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php
2008-03-07 20:06:03 +00:00
</p>
</li><li>Allow text search dictionary to filter out only stop words
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php">http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php</a>
Add: > > * Consider a function-based API for '@@' full text searches > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php >
2008-03-08 17:57:21 +00:00
</p>
Add: > > * Consider a special data type for regular expressions > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
2008-03-12 19:41:23 +00:00
</li><li>Consider a function-based API for '@@' full text searches
Add: > > * Consider a function-based API for '@@' full text searches > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php >
2008-03-08 17:57:21 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php</a>
Added to TODO: > * Improve text search error messages > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php > > > * Fix /contrib/ltree operator > > http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php
2008-03-17 22:34:23 +00:00
</p>
</li><li>Improve text search error messages
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php</a>
Add URL for: * Improve text search error messages > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php
2008-03-17 22:45:20 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php</a>
Add: > > * Consider a special data type for regular expressions > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
2008-03-12 19:41:23 +00:00
</p>
</li><li>Consider a special data type for regular expressions
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php</a>
Add: > > * Reduce BIT data type overhead using short varlena headers > > http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php
2008-03-17 23:49:33 +00:00
</p>
</li><li>Reduce BIT data type overhead using short varlena headers
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php">http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php</a>
Add to TODO: > > * Allow xml arrays to be cast to other data types > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php >
2008-03-24 23:46:21 +00:00
</p>
</li><li>Allow xml arrays to be cast to other data types
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php</a>
Add URL's for sequence discussions: > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > < o %Have ALTER TABLE RENAME rename SERIAL sequence names > o Have ALTER TABLE RENAME rename SERIAL sequence names > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
2008-03-03 15:06:55 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>Dates and Times
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Add intervals: > o Allow infinite dates and intervals just like infinite timestamps
2006-02-25 16:34:52 +00:00
<li>Allow infinite dates and intervals just like infinite timestamps
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Merge hardwired timezone names with the TZ database; allow either
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
kind everywhere a TZ name is currently taken
</li><li>Allow TIMESTAMP WITH TIME ZONE to store the original timezone
information, either zone name or offset from UTC [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?timezone">timezone</a>]
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
<p> If the TIMESTAMP value is stored with a time zone name, interval
Update. < computations should adjust based on the time zone rules, e.g. < adding 24 hours to a timestamp would yield a different result from < adding one day. < > computations should adjust based on the time zone rules.
2005-07-10 05:06:42 +00:00
computations should adjust based on the time zone rules.
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</p>
Add: > o Issue a warning if a change-on-restart-only postgresql.conf value > is modified and the server config files are reloaded > o Mark change-on-restart-only values in postgresql.conf 205a209 > o Fix SELECT '0.01 years'::interval, '0.01 months'::interval
2005-08-26 20:38:57 +00:00
</li><li>Fix SELECT '0.01 years'::interval, '0.01 months'::interval
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Add a GUC variable to allow output of interval values in ISO8601
Add items from Tom: < o Add a GUC variable to allow output of interval values in ISO8601 < format 212a211,223 > o Add a GUC variable to allow output of interval values in ISO8601 > format > o Improve timestamptz subtraction to be DST-aware > > Currently, subtracting one date from another that crosses a > daylight savings time adjustment can return '1 day 1 hour', but > adding that back to the first date returns a time one hour in > the future. This is caused by the adjustment of '25 hours' to > '1 day 1 hour', and '1 day' is the same time the next day, even > if daylight savings adjustments are involved. > > o Fix interval display to support values exceeding 2^31 hours > o Add overflow checking to timestamp and interval arithmetic
2005-10-27 02:33:31 +00:00
format
Add: > o Have timestamp subtraction not call justify_hours()? > > http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php > < o Add overflow checking to timestamp and interval arithmetic > o Add overflow checking to timestamp and interval arithmetic
2007-04-02 22:46:10 +00:00
</li><li>Have timestamp subtraction not call justify_hours()?
<p> <a href="http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php">http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php</a>
</p>
Add items from Tom: < o Add a GUC variable to allow output of interval values in ISO8601 < format 212a211,223 > o Add a GUC variable to allow output of interval values in ISO8601 > format > o Improve timestamptz subtraction to be DST-aware > > Currently, subtracting one date from another that crosses a > daylight savings time adjustment can return '1 day 1 hour', but > adding that back to the first date returns a time one hour in > the future. This is caused by the adjustment of '25 hours' to > '1 day 1 hour', and '1 day' is the same time the next day, even > if daylight savings adjustments are involved. > > o Fix interval display to support values exceeding 2^31 hours > o Add overflow checking to timestamp and interval arithmetic
2005-10-27 02:33:31 +00:00
</li><li>Improve timestamptz subtraction to be DST-aware
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently subtracting one date from another that crosses a
Add items from Tom: < o Add a GUC variable to allow output of interval values in ISO8601 < format 212a211,223 > o Add a GUC variable to allow output of interval values in ISO8601 > format > o Improve timestamptz subtraction to be DST-aware > > Currently, subtracting one date from another that crosses a > daylight savings time adjustment can return '1 day 1 hour', but > adding that back to the first date returns a time one hour in > the future. This is caused by the adjustment of '25 hours' to > '1 day 1 hour', and '1 day' is the same time the next day, even > if daylight savings adjustments are involved. > > o Fix interval display to support values exceeding 2^31 hours > o Add overflow checking to timestamp and interval arithmetic
2005-10-27 02:33:31 +00:00
daylight savings time adjustment can return '1 day 1 hour', but
adding that back to the first date returns a time one hour in
the future. This is caused by the adjustment of '25 hours' to
'1 day 1 hour', and '1 day' is the same time the next day, even
if daylight savings adjustments are involved.
</p>
</li><li>Fix interval display to support values exceeding 2^31 hours
Add: > o Have timestamp subtraction not call justify_hours()? > > http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php > < o Add overflow checking to timestamp and interval arithmetic > o Add overflow checking to timestamp and interval arithmetic
2007-04-02 22:46:10 +00:00
</li><li>Add overflow checking to timestamp and interval arithmetic
Add: > o Extend timezone code to allow 64-bit values so we can > represent years beyond 2038 > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php >
2007-01-11 04:27:29 +00:00
</li><li>Extend timezone code to allow 64-bit values so we can
represent years beyond 2038
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php</a>
Add: > > o Use LC_TIME for localized weekday/month names, rather than > LC_MESSAGES > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
2007-02-14 21:00:17 +00:00
</p>
</li><li>Use LC_TIME for localized weekday/month names, rather than
LC_MESSAGES
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php</a>
Add: > o Extend timezone code to allow 64-bit values so we can > represent years beyond 2038 > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php >
2007-01-11 04:27:29 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>Add ISO INTERVAL handling
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li></ul>
</li></ul>
Add URL for ISO dates: > http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php
2006-06-16 21:41:24 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php">http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php</a><br/>
<a href="http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php">http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php</a>
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</p>
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>Support ISO INTERVAL syntax if units cannot be determined from
Update SQL-standard INTERVAL item: o 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.
2006-04-25 00:01:44 +00:00
the string, and are supplied after the string
Word wrap entry
2006-04-25 00:06:23 +00:00
<p> 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'.
Update SQL-standard INTERVAL item: o 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.
2006-04-25 00:01:44 +00:00
</p>
<p> 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,
Word wrap entry
2006-04-25 00:06:23 +00:00
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'.
</p>
<p> 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.
Update SQL-standard INTERVAL item: o 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.
2006-04-25 00:01:44 +00:00
</p>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR
TO MONTH
</li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1
year' AS INTERVAL MONTH), and this should return '12 months'
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li><li>Round or truncate values to the requested precision, e.g.
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
INTERVAL '11 months' AS YEAR should return one or zero
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
<li>Arrays
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>Delay resolution of array expression's data type so assignment
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
coercion can be performed on empty array expressions
Add: < * Add support for arrays of domains > o Add support for arrays of domains > o Add support for arrays of complex types
2006-08-17 06:48:38 +00:00
</li><li>Add support for arrays of domains
Mark as done, add URL for other item: < o Add support for arrays of complex types > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php > > o -Add support for arrays of complex types
2007-05-13 11:22:04 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php">http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php</a>
</p>
Update text, per Greg Stark: < o Allow single-byte header storage for arrays > o Allow single-byte header storage for array elements
2007-04-11 21:02:31 +00:00
</li><li>Allow single-byte header storage for array elements
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li></ul>
</li><li>Binary Data
<ul>
Change /contrib to contrib for consistency.
2008-01-24 06:23:33 +00:00
<li>Improve vacuum of large objects, like contrib/vacuumlo?
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li><li>Add security checking for large objects
</li><li>Auto-delete large objects when referencing row is deleted
Change /contrib to contrib for consistency.
2008-01-24 06:23:33 +00:00
<p> contrib/lo offers this functionality.
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</p>
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li><li>Allow read/write into TOAST values like large objects
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> This requires the TOAST column to be stored EXTERNAL.
Add: > > o Add API for 64-bit large object access > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
2006-06-14 19:32:48 +00:00
</p>
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li><li>Add API for 64-bit large object access
Add: > > o Add API for 64-bit large object access > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
2006-06-14 19:32:48 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add URL for ISO date/time syntax: > > http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php >
2006-06-16 16:59:30 +00:00
</li></ul>
Add: < * -Make 64-bit version of the 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 < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the 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 > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
2007-11-26 23:31:09 +00:00
</li><li>MONEY data type
<ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<li>Add locale-aware MONEY type, and support multiple currencies
Add: < * -Make 64-bit version of the 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 < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the 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 > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
2007-11-26 23:31:09 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php">http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php</a>
</p>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
</li><li>MONEY dumps in a locale-specific format making it difficult to
Add: < * -Make 64-bit version of the 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 < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the 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 > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
2007-11-26 23:31:09 +00:00
restore to a system with a different locale
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Allow MONEY to be easily cast to/from other numeric data types
Add: < * -Make 64-bit version of the 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 < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the 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 > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
2007-11-26 23:31:09 +00:00
</li></ul>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li></ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<h1><a name="section_4">Functions</a></h1>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
<ul>
Remove completed items: < * -Allow limits on per-db/role connections 43d41 < * -Prevent dropping user that still owns objects, or auto-drop the objects 49d46 < * -Add the client IP address and port to pg_stat_activity < * -Add session start time and last statement time to pg_stat_activity < * -Add a function that returns the start time of the postmaster 230d224 < o -Allow MIN()/MAX() on arrays < o -Modify array literal representation to handle array index lower bound < of other than one 253d244 < * -Add function to return compressed length of TOAST data values < * -Prevent to_char() on interval from returning meaningless values < < For example, to_char('1 month', 'mon') is meaningless. Basically, < most date-related parameters to to_char() are meaningless for < intervals because interval is not anchored to a date. < < * -Have views on temporary tables exist in the temporary namespace < * -Allow temporary views on non-temporary tables 329d311 < * -Add BETWEEN SYMMETRIC/ASYMMETRIC < * -Add E'' escape string marker so eventually ordinary strings can treat < backslashes literally, for portability < < * -Allow additional tables to be specified in DELETE for joins < < UPDATE already allows this (UPDATE...FROM) but we need similar < functionality in DELETE. It's been agreed that the keyword should < be USING, to avoid anything as confusing as DELETE FROM a FROM b. < 341d313 < * -Allow REINDEX to rebuild all database indexes < * -Add an option to automatically use savepoints for each statement in a < multi-statement transaction. < < When enabled, this would allow errors in multi-statement transactions < to be automatically ignored. < 426d391 < o -Allow FOR UPDATE queries to do NOWAIT locks 473d437 < o -Allow COPY to understand \x as a hex byte < o -Allow COPY to optionally include column headings in the first line < o -Allow COPY FROM ... CSV to interpret newlines and carriage < returns in data 525d485 < o -Have SHOW ALL show descriptions for server-side variables < o -Allow PL/PgSQL's RAISE function to take expressions < < Currently only constants are supported. < < o -Change PL/PgSQL to use palloc() instead of malloc() 545d499 < o -Allow PL/pgSQL EXECUTE query_var INTO record_var; 550d503 < o -Pass arrays natively instead of as text between plperl and postgres 598d550 < o -Add dumping and restoring of LOB comments 638d589 < * -Implement shared row locks and use them in RI triggers 642d592 < * -Allow triggers to be disabled < * -Add two-phase commit < < < * -Prevent inherited tables from expanding temporary subtables of other < sessions < * -Use indexes for MIN() and MAX() < < MIN/MAX queries can already be rewritten as SELECT col FROM tab ORDER < BY col {DESC} LIMIT 1. Completing this item involves doing this < transformation automatically. < < * -Use index to restrict rows returned by multi-key index when used with < non-consecutive keys to reduce heap accesses < < For an index on col1,col2,col3, and a WHERE clause of col1 = 5 and < col3 = 9, spin though the index checking for col1 and col3 matches, < rather than just col1; also called skip-scanning. < < * -Fetch heap pages matching index entries in sequential order < < Rather than randomly accessing heap pages based on index entries, mark < heap pages needing access in a bitmap and do the lookups in sequential < order. Another method would be to sort heap ctids matching the index < before accessing the heap rows. < < * -Allow non-bitmap indexes to be combined by creating bitmaps in memory < < This feature allows separate indexes to be ANDed or ORed together. This < is particularly useful for data warehousing applications that need to < query the database in an many permutations. This feature scans an index < and creates an in-memory bitmap, and allows that bitmap to be combined < with other bitmap created in a similar way. The bitmap can either index < all TIDs, or be lossy, meaning it records just page numbers and each < page tuple has to be checked for validity in a separate pass. < < * -Fix incorrect rtree results due to wrong assumptions about "over" < operator semantics 782d694 < o -Add concurrency to GIST 813d724 < * -Allow multiple blocks to be written to WAL with one write() < * -Consider use of open/fcntl(O_DIRECT) to minimize OS caching, < for WAL writes < < O_DIRECT doesn't have the same media write guarantees as fsync, so it < is in addition to the fsync method, not in place of it. < < * -Cache last known per-tuple offsets to speed long tuple access < * -Allow the size of the buffer cache used by temporary objects to be < specified as a GUC variable < < Larger local buffer cache sizes requires more efficient handling of < local cache lookups. < < * -Improve the background writer < < Allow the background writer to more efficiently write dirty buffers < from the end of the LRU cache and use a clock sweep algorithm to < write other dirty buffers to reduced checkpoint I/O < 897d788 < * -Add a warning when the free space map is too small 917d807 < o -Move into the backend code < * -Make locking of shared data structures more fine-grained < < This requires that more locks be acquired but this would reduce lock < contention, improving concurrency. < < * -Improve SMP performance on i386 machines < < i386-based SMP machines can generate excessive context switching < caused by lock failure in high concurrency situations. This may be < caused by CPU cache line invalidation inefficiencies. < 979d857 < o -Add ability to turn off full page writes < * -Eliminate WAL logging for CREATE TABLE AS when not doing WAL archiving < * -Change WAL to use 32-bit CRC, for performance reasons < < * -Use CHECK constraints to influence optimizer decisions < < CHECK constraints contain information about the distribution of values < within the table. This is also useful for implementing subtables where < a tables content is distributed across several subtables. < 1045d913 < * -ANALYZE should record a pg_statistic entry for an all-NULL column 1099d966 < * -Remove kerberos4 from source tree 1103d969 < * -Make src/port/snprintf.c thread-safe 1118d983 < * -Add C code on Unix to copy directories for use in creating new databases 1133d997 < o -Improve dlerror() reporting string
2005-08-26 18:59:48 +00:00
<li>Allow INET subnet tests using non-constants to be indexed
Add: > * Allow to_date() and to_timestamp() accept localized month names
2006-03-03 02:18:09 +00:00
</li><li>Allow to_date() and to_timestamp() accept localized month names
Add: > * Fix to_date()-related functions to consistently issue errors > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php >
2007-04-02 21:25:34 +00:00
</li><li>Fix to_date()-related functions to consistently issue errors
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php</a>
</p>
Add: > * Add missing parameter handling in to_char() > > http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php >
2006-03-03 02:38:57 +00:00
</li><li>Add missing parameter handling in to_char()
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php">http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php</a>
Add: > * Add missing parameter handling in to_char() > > http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php >
2006-03-03 02:38:57 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Allow substring/replace() to get/set bit values
</li><li>Allow to_char() on interval values to accumulate the highest unit
requested
<p> Some special format flag would be required to request such
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
accumulation. Such functionality could also be added to EXTRACT.
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
Prevent accumulation that crosses the month/day boundary because of
the uneven number of days in a month.
</p>
<ul>
<li>to_char(INTERVAL '1 hour 5 minutes', 'MI') =&gt; 65
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>to_char(INTERVAL '43 hours 20 minutes', 'MI' ) =&gt; 2600
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') =&gt; 0:1:19:20
</li><li>to_char(INTERVAL '3 years 5 months','MM') =&gt; 41
</li></ul>
Mark TODO item "autovacuum on by default" as completed.
2007-01-17 03:43:49 +00:00
</li><li>Implement inlining of set-returning functions defined in SQL
Add: > * Allow SQL-language functions to return results from RETURNING queries
2006-11-23 05:01:47 +00:00
</li><li>Allow SQL-language functions to return results from RETURNING queries
Add URL for: * Allow SQL-language functions to return results from RETURNING queries > > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php >
2007-02-14 02:49:37 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php</a>
Add: * Allow SQL-language functions to reference parameters by parameter name Currently SQL-language functions can only refer to parameters via $1, etc
2007-02-18 01:32:55 +00:00
</p>
</li><li>Allow SQL-language functions to reference parameters by parameter name
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently SQL-language functions can only refer to dollar parameters,
e.g. $1
Add URL for: * Allow SQL-language functions to return results from RETURNING queries > > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php >
2007-02-14 02:49:37 +00:00
</p>
Add: > * Allow holdable cursors in SPI
2007-02-17 02:01:02 +00:00
</li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
Add: > * Enforce typmod for function inputs, function results and parameters for > spi_prepare'd statements called from PLs > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php
2007-01-27 03:25:49 +00:00
</li><li>Enforce typmod for function inputs, function results and parameters for
spi_prepare'd statements called from PLs
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php</a>
Add: > > * Tighten function permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
2007-02-01 04:50:58 +00:00
</p>
Add: > * Allow holdable cursors in SPI
2007-02-17 02:01:02 +00:00
</li><li>Allow holdable cursors in SPI
Add: > > * Tighten function permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
2007-02-01 04:50:58 +00:00
</li><li>Tighten function permission checks
Update URL for function permission checks < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php >
2007-02-01 04:51:31 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php</a>
Add: > * Fix IS OF so it matches the ISO specification, and add documentation > > http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
2007-02-20 14:17:24 +00:00
</p>
</li><li>Fix IS OF so it matches the ISO specification, and add documentation
<p> <a href="http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php">http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php</a>
Add: > > * Add missing operators for geometric data types > > Some geometric types do not have the full suite of geometric operators, > e.g. box @> point >
2007-02-20 21:22:35 +00:00
</p>
</li><li>Add missing operators for geometric data types
<p> Some geometric types do not have the full suite of geometric operators,
e.g. box @&gt; point
Add: > * Implement Boyer-Moore searching in strpos() > > http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php
2007-09-26 08:47:43 +00:00
</p>
</li><li>Implement Boyer-Moore searching in strpos()
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php">http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php</a>
Add: > * Prevent malicious functions from being executed with the permissions > of unsuspecting users > > 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
2008-03-06 17:19:38 +00:00
</p>
</li><li>Prevent malicious functions from being executed with the permissions
of unsuspecting users
<p> Index functions are safe, so VACUUM and ANALYZE are safe too.
Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php</a>
Add: > > * Reduce memory usage of aggregates in set returning functions > > http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php >
2008-03-06 18:00:59 +00:00
</p>
</li><li>Reduce memory usage of aggregates in set returning functions
<p> <a href="http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php">http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php</a>
Add: > > * Add temporal versions of generate_series() > > http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php
2008-03-11 17:42:13 +00:00
</p>
</li><li>Add temporal versions of generate_series()
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php</a>
Add to TODO: > > * Add array_accum() and array_to_set() functions for arrays > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php
2008-03-12 15:14:50 +00:00
</p>
</li><li>Add array_accum() and array_to_set() functions for arrays
Update TODO: * Add array_accum() and array_to_set() functions for arrays The standards specify array_agg() and UNNEST. http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php
2008-03-12 19:32:07 +00:00
<p> The standards specify array_agg() and UNNEST.
<a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php</a>
Added to TODO: > * Improve text search error messages > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php > > > * Fix /contrib/ltree operator > > http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php
2008-03-17 22:34:23 +00:00
</p>
</li><li>Fix /contrib/ltree operator
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php">http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php</a>
Add: > > * Fix inconsistent precedence of =, >, and < compared to <>, >=, and <= > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php
2008-03-21 19:58:11 +00:00
</p>
</li><li>Fix inconsistent precedence of =, &gt;, and &lt; compared to &lt;&gt;, &gt;=, and &lt;=
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php">http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php</a>
Add to TODO: > > * Fix regular expression bug when using complex back-references > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php
2008-03-25 00:00:30 +00:00
</p>
</li><li>Fix regular expression bug when using complex back-references
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php">http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php</a>
Add to TODO: > > * Have /contrib/dblink reuse unnamed connections > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php
2008-03-25 00:07:12 +00:00
</p>
</li><li>Have /contrib/dblink reuse unnamed connections
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php</a>
Add: > * Enforce typmod for function inputs, function results and parameters for > spi_prepare'd statements called from PLs > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php
2007-01-27 03:25:49 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<h1><a name="section_5">Multi-Language Support</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Add NCHAR (as distinguished from ordinary varchar),
</li><li>Allow locale to be set at database creation
Add description: < Currently locale can only be set during initdb. > Currently locale can only be set during initdb. No global tables have > locale-aware columns. However, the database template used during > database creation might have locale-aware indexes. The indexes would > need to be reindexed to match the new locale.
2005-05-07 15:45:23 +00:00
<p> Currently locale can only be set during initdb. No global tables have
locale-aware columns. However, the database template used during
database creation might have locale-aware indexes. The indexes would
need to be reindexed to match the new locale.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add URLs < * Allow encoding on a per-column basis > * Allow encoding on a per-column basis optionally using the ICU library: > http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php > http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php
2006-08-11 15:53:39 +00:00
</li><li>Allow encoding on a per-column basis optionally using the ICU library:
Add locale/encoding references: < Right now only one encoding is allowed per database. > Right now only one encoding is allowed per database. [locale] > * Add CREATE COLLATE? [locale]
2006-06-14 18:47:53 +00:00
<p> Right now only one encoding is allowed per database. [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php">http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php</a>
Add URLs < * Allow encoding on a per-column basis > * Allow encoding on a per-column basis optionally using the ICU library: > http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php > http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php
2006-08-11 15:53:39 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php">http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php</a>
Add recent ICU URL: > http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php
2006-09-14 17:14:53 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add locale/encoding references: < Right now only one encoding is allowed per database. > Right now only one encoding is allowed per database. [locale] > * Add CREATE COLLATE? [locale]
2006-06-14 18:47:53 +00:00
</li><li>Add CREATE COLLATE? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Support multiple simultaneous character sets, per SQL92
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Improve UTF8 combined character handling?
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Add octet_length_server() and octet_length_client()
</li><li>Make octet_length_client() the same as octet_length()?
Add: > * Fix problems with wrong runtime encoding conversion for NLS message files
2005-08-21 01:04:45 +00:00
</li><li>Fix problems with wrong runtime encoding conversion for NLS message files
Add information schema item: > * Improve the information schema to be more standards-compliant: > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php > * Add URL to more complete multi-byte regression tests > > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php < * Add URL to more complete multi-byte regression tests < < http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
2006-06-14 21:10:50 +00:00
</li><li>Add URL to more complete multi-byte regression tests
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php">http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php</a>
Add item, not fixed: > > * Fix ILIKE and regular expressions to handle case insensitivity > properly in multibyte encodings > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
2006-06-14 21:40:00 +00:00
</p>
</li><li>Fix ILIKE and regular expressions to handle case insensitivity
properly in multibyte encodings
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php">http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php</a>
Add URL to ILIKE encoding fix: > http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
2006-06-14 23:03:12 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php</a>
Add item: > > * Set client encoding based on the client operating system encoding > > Currently client_encoding is set in postgresql.conf, which > defaults to the server encoding.
2006-09-18 15:52:23 +00:00
</p>
</li><li>Set client encoding based on the client operating system encoding
<p> Currently client_encoding is set in postgresql.conf, which
defaults to the server encoding.
Add: > * Prevent malicious functions from being executed with the permissions > of unsuspecting users > > 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
2008-03-06 17:19:38 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php</a>
Add: > > * Change memory allocation for multi-byte functions so memory is > allocated inside conversion functions > > Currently we preallocate memory based on worst-case usage.
2008-03-11 19:44:39 +00:00
</p>
</li><li>Change memory allocation for multi-byte functions so memory is
allocated inside conversion functions
<p> Currently we preallocate memory based on worst-case usage.
Add information schema item: > * Improve the information schema to be more standards-compliant: > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php > * Add URL to more complete multi-byte regression tests > > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php < * Add URL to more complete multi-byte regression tests < < http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
2006-06-14 21:10:50 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<h1><a name="section_6">Views / Rules</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Done: > * -Add 'tid != tid ' operator for use in corruption recovery
2006-02-26 21:22:47 +00:00
<li>Automatically create rules on views so they are updateable, per SQL99
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> We can only auto-create rules for simple views. For more complex
Done: > * -Add 'tid != tid ' operator for use in corruption recovery
2006-02-26 21:22:47 +00:00
cases users will still have to write rules manually.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php</a>
Add URL for: * Automatically create rules on views so they are updateable, per SQL99 > http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php
2007-03-28 02:17:45 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php">http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li><li>Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
</li><li>Allow NOTIFY in rules involving conditionals
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</li><li>Allow VIEW/RULE recompilation when the underlying tables change
Update: > > Another issue is whether underlying table changes should be reflected > in the view, e.g. should SELECT * show additional columns if they > are added after the view is created.
2005-08-27 13:38:43 +00:00
<p> Another issue is whether underlying table changes should be reflected
in the view, e.g. should SELECT * show additional columns if they
are added after the view is created.
Add: > > * Make it possible to use RETURNING together with conditional DO INSTEAD > rules, such as for partitioning setups > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
2007-09-14 18:50:48 +00:00
</p>
</li><li>Make it possible to use RETURNING together with conditional DO INSTEAD
rules, such as for partitioning setups
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php</a>
Add: > > * Add the ability to automatically create materialized views > > Right now materialized views require the user to create triggers on the > main table to keep the summary table current. SQL syntax should be able > to manager the triggers and summary table automatically. A more > sophisticated implementation would automatically retrieve from the > summary table when the main table is referenced, if possible. >
2008-01-14 22:14:30 +00:00
</p>
</li><li>Add the ability to automatically create materialized views
<p> Right now materialized views require the user to create triggers on the
main table to keep the summary table current. SQL syntax should be able
to manager the triggers and summary table automatically. A more
sophisticated implementation would automatically retrieve from the
summary table when the main table is referenced, if possible.
Update: > > Another issue is whether underlying table changes should be reflected > in the view, e.g. should SELECT * show additional columns if they > are added after the view is created.
2005-08-27 13:38:43 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<h1><a name="section_7">SQL Commands</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Remove: < * Change LIMIT/OFFSET and FETCH/MOVE to use int8
2006-09-03 13:37:38 +00:00
<li>Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Allow SET CONSTRAINTS to be qualified by schema/table name
</li><li>%Add a separate TRUNCATE permission
Add: > * Add TRUNCATE permission > > Currently only the owner can TRUNCATE a table because triggers are not > called, and the table is locked in exclusive mode. >
2005-07-30 03:15:22 +00:00
<p> Currently only the owner can TRUNCATE a table because triggers are not
called, and the table is locked in exclusive mode.
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Allow PREPARE of cursors
</li><li>Allow finer control over the caching of prepared query plans
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently queries prepared via the libpq API are planned on first
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
execute using the supplied parameters --- allow SQL PREPARE to do the
same. Also, allow control over replanning prepared queries either
manually or automatically when statistics for execute parameters
differ dramatically from those used during planning.
</p>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Improve logging of prepared transactions recovered during startup
Add: > * Improve logging of prepared statements recovered during startup > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php >
2007-02-14 04:19:37 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
<p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
such information in memory would improve performance.
</p>
</li><li>Add optional textual message to NOTIFY
<p> This would allow an informational message to be added to the notify
message, perhaps indicating the row modified or other custom
information.
Add: > * Allow pg_ctl to work properly with configuration files located outside > the PGDATA directory > > pg_ctl can not read the pid file because it isn't located in the > config directory but in the PGDATA directory. The solution is to > allow pg_ctl to read and understand postgresql.conf to find the > data_directory value. >
2005-06-04 18:12:38 +00:00
</p>
Add: > * Allow multiple identical NOTIFY events to always be communicated to the > client, rather than sent as a single notification to the listener
2008-01-03 18:47:44 +00:00
</li><li>Allow multiple identical NOTIFY events to always be communicated to the
client, rather than sent as a single notification to the listener
Add URL for: * Allow multiple identical NOTIFY events to always be communicated to the client, rather than sent as a single notification to the listener http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
2008-03-07 18:53:49 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php">http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries
Split out MERGE and REPLACE/UPSERT items. < * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, < triggers?) > * Add SQL-standard MERGE command, typically used to merge two tables > > This is similar to UPDATE, then for unmatched rows, INSERT. > Whether concurrent access allows modifications which could cause > row loss is implementation independent. > > * Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
2005-12-01 22:07:59 +00:00
</li><li>Add SQL-standard MERGE command, typically used to merge two tables
Add MERGE TODO.detail: > [merge] 378a380 > [merge]
2005-12-01 22:12:35 +00:00
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
Split out MERGE and REPLACE/UPSERT items. < * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, < triggers?) > * Add SQL-standard MERGE command, typically used to merge two tables > > This is similar to UPDATE, then for unmatched rows, INSERT. > Whether concurrent access allows modifications which could cause > row loss is implementation independent. > > * Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
2005-12-01 22:07:59 +00:00
<p> This is similar to UPDATE, then for unmatched rows, INSERT.
Whether concurrent access allows modifications which could cause
row loss is implementation independent.
</p>
</li><li>Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
Add MERGE TODO.detail: > [merge] 378a380 > [merge]
2005-12-01 22:12:35 +00:00
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
Update MERGE: > > To implement this cleanly requires that the table have a unique index > so duplicate checking can be easily performed. >
2005-11-15 23:08:24 +00:00
<p> To implement this cleanly requires that the table have a unique index
Update, add mention of user locking table before MERGE: < so duplicate checking can be easily performed. > so duplicate checking can be easily performed. It is possible to > do it without a unique index if we require the user to LOCK the table > before the MERGE.
2005-11-16 18:45:09 +00:00
so duplicate checking can be easily performed. It is possible to
do it without a unique index if we require the user to LOCK the table
before the MERGE.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00501.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00501.php</a>
Add URLs for: * Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT [merge]
2007-03-03 03:08:46 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00536.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00536.php</a>
Update MERGE: > > To implement this cleanly requires that the table have a unique index > so duplicate checking can be easily performed. >
2005-11-15 23:08:24 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
creation
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
</li><li>Add GUC to issue notice about statements that use unjoined tables
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Allow EXPLAIN to identify tables that were skipped because of
enable_constraint_exclusion => constraint_exclusion Also improve wording.
2005-08-22 17:35:03 +00:00
constraint_exclusion
Update item: < * Allow EXPLAIN output to be more easily processed by scripts > * Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
2007-06-13 21:38:00 +00:00
</li><li>Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
</li><li>Enable standard_conforming_strings
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Make standard_conforming_strings the default in 8.5?
Add: < * -Eventually enable escape_string_warning and standard_conforming_strings > * -Enable escape_string_warning and standard_conforming_strings > * Make standard_conforming_strings the default in 8.3? > > When this is done, backslash-quote should be prohibited in non-E'' > strings because of possible confusion over how such strings treat > backslashes. Basically, '' is always safe for a literal single > quote, while \' might or might not be based on the backslash > handling rules. >
2006-04-23 04:00:06 +00:00
<p> When this is done, backslash-quote should be prohibited in non-E''
strings because of possible confusion over how such strings treat
backslashes. Basically, '' is always safe for a literal single
quote, while \' might or might not be based on the backslash
handling rules.
</p>
Add: > * Simplify dropping roles that have objects in several databases
2005-09-23 21:55:01 +00:00
</li><li>Simplify dropping roles that have objects in several databases
Add: > * Allow COMMENT ON to accept an expression rather than just a string
2005-11-28 22:21:58 +00:00
</li><li>Allow COMMENT ON to accept an expression rather than just a string
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Allow the count returned by SELECT, etc to be represented as an int64
Add: > * Allow the count returned by SELECT, etc to be to represent as an int64 > to allow a higher range of values
2005-12-17 01:48:37 +00:00
to allow a higher range of values
Move items: > * Add SQL99 WITH clause to SELECT > * Add SQL99 WITH RECURSIVE to SELECT < * Add SQL99 WITH clause to SELECT < * Add SQL99 WITH RECURSIVE to SELECT
2006-02-01 00:07:26 +00:00
</li><li>Add SQL99 WITH clause to SELECT
Update: < * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT > * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
2006-06-09 01:02:22 +00:00
</li><li>Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Add URL for: * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php
2008-03-06 22:04:57 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php</a>
Add URL for: * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php
2008-03-06 22:15:27 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php</a>
Add URL for: * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01334.php
2008-03-17 22:54:23 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg01334.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg01334.php</a>
Add URL for: * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php >
2008-03-05 16:02:31 +00:00
</p>
Add/ cleanup: < * %Disallow changing default expression of a SERIAL column? > * %Disallow changing DEFAULT expression of a SERIAL column? 472a473,476 > * Add DEFAULT .. AS OWNER so permission checks are done as the table > owner > > This would be useful for SERIAL nextval() calls and CHECK constraints.
2006-05-05 09:35:58 +00:00
</li><li>Add DEFAULT .. AS OWNER so permission checks are done as the table
owner
<p> This would be useful for SERIAL nextval() calls and CHECK constraints.
</p>
Updates per Tom: > * Allow DISTINCT to work in multiple-argument aggregate calls < o Allow UPDATE to handle complex aggregates [update]?
2006-07-28 19:00:45 +00:00
</li><li>Allow DISTINCT to work in multiple-argument aggregate calls
Add entry: > * Add column to pg_stat_activity that shows the progress of long-running > commands like CREATE INDEX and VACUUM
2006-07-29 18:08:36 +00:00
</li><li>Add column to pg_stat_activity that shows the progress of long-running
commands like CREATE INDEX and VACUUM
Add: < > * Implement SQL:2003 window functions
2006-08-25 23:43:46 +00:00
</li><li>Implement SQL:2003 window functions
Add: > * Improve failure message when DROP DATABASE is used on a database that > has prepared transactions
2007-02-13 19:57:09 +00:00
</li><li>Improve failure message when DROP DATABASE is used on a database that
has prepared transactions
Add: > * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause > > http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php >
2007-02-19 20:06:56 +00:00
</li><li>Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
<p> <a href="http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php">http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php</a>
Add: > * Increase locking when DROPing objects so dependent objects cannot > get dropped while the DROP operation is happening > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php
2007-02-20 22:29:28 +00:00
</p>
</li><li>Increase locking when DROPing objects so dependent objects cannot
get dropped while the DROP operation is happening
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php</a>
Add: > * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause > > http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php >
2007-02-19 20:06:56 +00:00
</p>
Move item as done: < > * -Allow AS in "SELECT col AS label" to be optional in certain cases > < * Allow AS in "SELECT col AS label" to be optional (not wanted)
2008-02-16 23:27:34 +00:00
</li><li>-<em>Allow AS in "SELECT col AS label" to be optional in certain cases</em>
Add: > * Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ... > RETURNING to supply values to the INSERT > http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979
2008-03-03 21:26:09 +00:00
</li><li>Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ...
RETURNING to supply values to the INSERT
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979">http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979</a>
Add: > > * Add comments on system tables/columns using the information in > catalogs.sgml > > Ideally the information would be pulled from the SGML file > automatically. >
2008-03-07 14:57:39 +00:00
</li><li>Add comments on system tables/columns using the information in
catalogs.sgml
<p> Ideally the information would be pulled from the SGML file
automatically.
Add to TODO: > * Improve reporting of UNION type mismatches > > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php
2008-03-24 16:05:45 +00:00
</p>
</li><li>Improve reporting of UNION type mismatches
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php">http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php</a>
Add: > > * Add comments on system tables/columns using the information in > catalogs.sgml > > Ideally the information would be pulled from the SGML file > automatically. >
2008-03-07 14:57:39 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>CREATE
<ul>
<li>Allow CREATE TABLE AS to determine column lengths for complex
expressions like SELECT col1 || col2
Add: > o Have WITH CONSTRAINTS also create constraint indexes > http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
2007-04-10 01:22:12 +00:00
</li><li>Have WITH CONSTRAINTS also create constraint indexes
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php">http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php</a>
Add: > > o Have CONSTRAINT cname NOT NULL preserve the contraint name > > Right now pg_attribute.attnotnull records the NOT NULL status > of the column, but does not record the contraint name >
2008-03-06 03:18:19 +00:00
</p>
Wording fix: < o Have CONSTRAINT cname NOT NULL preserve the contraint name > o Have CONSTRAINT cname NOT NULL record the contraint name
2008-03-06 03:22:32 +00:00
</li><li>Have CONSTRAINT cname NOT NULL record the contraint name
Add: > > o Have CONSTRAINT cname NOT NULL preserve the contraint name > > Right now pg_attribute.attnotnull records the NOT NULL status > of the column, but does not record the contraint name >
2008-03-06 03:18:19 +00:00
<p> Right now pg_attribute.attnotnull records the NOT NULL status
of the column, but does not record the contraint name
Add: > o Prevent concurrent CREATE TABLE table1 from sometimes returning > a cryptic error message > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php
2008-03-25 00:11:48 +00:00
</p>
</li><li>Prevent concurrent CREATE TABLE table1 from sometimes returning
a cryptic error message
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php">http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php</a>
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li></ul>
</li><li>UPDATE
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
Update: < Last updated: Sat Sep 2 08:31:04 EDT 2006 > Last updated: Sat Sep 2 16:31:46 EDT 2006 < o Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple < columns > o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating > multiple columns > o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) < A subselect can also be used as the value source.
2006-09-02 20:31:50 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php">http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php</a>
Add URL for: o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) < > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php
2007-04-03 01:16:24 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php</a>
Add TODO URLs for: o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) > http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php > http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php
2008-03-18 15:30:59 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php">http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php">http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php</a>
Update wording: o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
2007-06-01 18:40:42 +00:00
</p>
</li><li>Research self-referential UPDATEs that see inconsistent row versions
in read-committed mode
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php</a>
Add URL for: o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode < > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php
2007-06-01 18:41:55 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php</a>
Add: > > o Allow GLOBAL temporary tables to exist as empty by default in > all sessions > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php >
2007-07-18 00:16:21 +00:00
</p>
</li><li>Allow GLOBAL temporary tables to exist as empty by default in
all sessions
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php">http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php</a>
Add for UPDATE SET for multiple values: > > A subselect can also be used as the value source.
2006-07-27 22:01:34 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li></ul>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>ALTER
<ul>
Add URL's for sequence discussions: > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > < o %Have ALTER TABLE RENAME rename SERIAL sequence names > o Have ALTER TABLE RENAME rename SERIAL sequence names > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
2008-03-03 15:06:55 +00:00
<li>Have ALTER TABLE RENAME rename SERIAL sequence names
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php">http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php</a>
</p>
Add: > o Have ALTER SEQUENCE RENAME rename the sequence name stored > in the sequence table > > http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php >
2007-10-08 18:01:17 +00:00
</li><li>Have ALTER SEQUENCE RENAME rename the sequence name stored
in the sequence table
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php">http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php</a>
<a href="http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php">http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php</a>
Add URL's for sequence discussions: > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > < o %Have ALTER TABLE RENAME rename SERIAL sequence names > o Have ALTER TABLE RENAME rename SERIAL sequence names > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
2008-03-03 15:06:55 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php">http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php</a>
Add: > o Have ALTER SEQUENCE RENAME rename the sequence name stored > in the sequence table > > http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php >
2007-10-08 18:01:17 +00:00
</p>
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</li><li>Add ALTER DOMAIN to modify the underlying data type
Not done: > o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
2006-02-12 19:13:19 +00:00
</li><li>%Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php</a>
Add URL for ALTER CONSTRAINT RENAME. > > See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. >
2006-06-08 03:17:11 +00:00
</p>
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Allow ALTER TABLE to change constraint deferrability and actions
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</li><li>Add missing object types for ALTER ... SET SCHEMA
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Allow ALTER TABLESPACE to move to different directories
Remove idea of schema tablespaces: < o Allow databases and schemas to be moved to different tablespaces < < One complexity is whether moving a schema should move all existing < schema objects or just define the location for future object creation. < > o Allow databases to be moved to different tablespaces 484c480 < schema. Global system tables can never be moved. > tablespace. Global system tables can never be moved.
2005-06-09 03:00:43 +00:00
</li><li>Allow databases to be moved to different tablespaces
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Allow moving system tables to other tablespaces, where possible
<p> Currently non-global system tables must be in the default database
Remove idea of schema tablespaces: < o Allow databases and schemas to be moved to different tablespaces < < One complexity is whether moving a schema should move all existing < schema objects or just define the location for future object creation. < > o Allow databases to be moved to different tablespaces 484c480 < schema. Global system tables can never be moved. > tablespace. Global system tables can never be moved.
2005-06-09 03:00:43 +00:00
tablespace. Global system tables can never be moved.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add: > o Prevent parent tables from altering or dropping constraints > like CHECK that are inherited by child tables > > Dropping constraints should only be possible with CASCADE. >
2006-03-06 17:10:31 +00:00
</li><li>Prevent parent tables from altering or dropping constraints
Update inheritance constraint items: < o %Prevent child tables from altering or dropping constraints < like CHECK that were inherited from the parent table < like CHECK that are inherited by child tables < < Dropping constraints should only be possible with CASCADE. < > like CHECK that are inherited by child tables unless CASCADE > is used > o %Prevent child tables from altering or dropping constraints > like CHECK that were inherited from the parent table
2006-04-25 02:58:34 +00:00
like CHECK that are inherited by child tables unless CASCADE
is used
</li><li>%Prevent child tables from altering or dropping constraints
like CHECK that were inherited from the parent table
Add: > o Have ALTER INDEX update the name of a constraint using that index > o Allow ALTER TABLE RENAME CONSTRAINT
2005-10-27 14:07:29 +00:00
</li><li>Have ALTER INDEX update the name of a constraint using that index
Update: < o Allow ALTER TABLE RENAME CONSTRAINT > o Add ALTER TABLE RENAME CONSTRAINT, update index name also
2005-10-27 14:16:05 +00:00
</li><li>Add ALTER TABLE RENAME CONSTRAINT, update index name also
Add: > o Allow column display reordering by recording a display, > storage, and permanent id for every column? > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php >
2007-02-02 05:42:56 +00:00
</li><li>Allow column display reordering by recording a display,
storage, and permanent id for every column?
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li><li>CLUSTER
<ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<li>Automatically maintain clustering on a table
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> This might require some background daemon to maintain clustering
during periods of low usage. It might also require tables to be only
Force update.
2005-12-16 18:56:55 +00:00
partially filled for easier reorganization. Another idea would
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
be to create a merged heap/index data file so an index lookup would
automatically access the heap data too. A third idea would be to
store heap rows in hashed groups, perhaps using a user-supplied
hash function.
Add URL: > http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php
2006-08-09 16:42:19 +00:00
<a href="http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php">http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Add default clustering to system tables
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> To do this, determine the ideal cluster index for each system
table and set the cluster setting during initdb.
</p>
Add to TODO: CLUSTER: > > o %Add VERBOSE option to report tables as they are processed, > like VACUUM VERBOSE
2007-03-22 20:38:42 +00:00
</li><li>%Add VERBOSE option to report tables as they are processed,
like VACUUM VERBOSE
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li><li>COPY
<ul>
<li>Allow COPY to report error lines and continue
<p> This requires the use of a savepoint before each COPY line is
processed, with ROLLBACK on COPY failure.
Add URL for: o Allow COPY to report error lines and continue This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure. > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php
2008-03-18 00:23:41 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Update: > o Allow COPY on a newly-created table to skip WAL logging 450a452,456 > On crash recovery, the table involved in the COPY would > have its heap and index files truncated. One issue is > that no other backend should be able to add to the table > at the same time, which is something that is currently > allowed.
2005-09-02 21:10:59 +00:00
</li><li>Allow COPY on a newly-created table to skip WAL logging
<p> On crash recovery, the table involved in the COPY would
Update wording: < 390d388 < 453c451 < removed or have its heap and index files truncated. One > be removed or have its heap and index files truncated. One < * Use a phantom command counter for nested subtransactions to reduce < per-tuple overhead
2005-09-16 16:46:09 +00:00
be removed or have its heap and index files truncated. One
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
issue is that no other backend should be able to add to
the table at the same time, which is something that is
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
currently allowed. This currently is done if the table is
created inside the same transaction block as the COPY because
no other backends can see the table.
Add another URL for: o Consider using a ring buffer for COPY FROM < < http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php
2008-03-03 21:00:35 +00:00
</p>
</li><li>Consider using a ring buffer for COPY FROM
<p> <a href="http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php">http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php</a>
Add: > > o Allow COPY FROM to create index entries in bulk > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php >
2008-03-05 15:56:11 +00:00
</p>
</li><li>Allow COPY FROM to create index entries in bulk
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php</a>
add to TODO COPY: > > o Allow COPY in CSV mode to control whether "" is treated as NULL > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00905.php
2008-03-11 22:47:28 +00:00
</p>
Update TODO: o Allow COPY in CSV mode to control whether a quoted zero-length string is treated as NULL Currently this is always treated as a zero-length string, which generates an error when loading into an integer column
2008-03-11 23:17:05 +00:00
</li><li>Allow COPY in CSV mode to control whether a quoted zero-length
string is treated as NULL
<p> Currently this is always treated as a zero-length string,
which generates an error when loading into an integer column
<a href="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2007-07/msg00905.php</a>
Update: > o Allow COPY on a newly-created table to skip WAL logging 450a452,456 > On crash recovery, the table involved in the COPY would > have its heap and index files truncated. One issue is > that no other backend should be able to add to the table > at the same time, which is something that is currently > allowed.
2005-09-02 21:10:59 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>GRANT/REVOKE
<ul>
<li>Allow column-level privileges
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Allow GRANT/REVOKE permissions to be applied to all schema objects
Done: < o Allow objects to be moved to different schemas > o -Allow objects to be moved to different schemas Fix word wrap: < * Allow GRANT/REVOKE permissions to be applied to all schema objects with one < command > o Allow GRANT/REVOKE permissions to be applied to all schema objects > with one command
2005-08-01 14:05:03 +00:00
with one command
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
<p> The proposed syntax is:
</p><p> GRANT SELECT ON ALL TABLES IN public TO phpuser;
GRANT SELECT ON NEW TABLES IN public TO phpuser;
</p>
Cleanups: < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table?
2006-06-09 18:41:57 +00:00
</li><li>Allow GRANT/REVOKE permissions to be inherited by objects based on
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
schema permissions
Cleanups: < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table?
2006-06-09 18:41:57 +00:00
</li><li>Allow SERIAL sequences to inherit permissions from the base table?
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>CURSOR
<ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<li>Prevent DROP TABLE from dropping a row referenced by its own open
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
cursor?
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li><li>INSERT
<ul>
<li>Allow INSERT/UPDATE of the system-generated oid value for a row
Done: < o Allow INSERT/UPDATE ... RETURNING new.col or old.col < < This is useful for returning the auto-generated key for an INSERT. < One complication is how to handle rules that run as part of < the insert. < http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php > o -Allow INSERT/UPDATE ... RETURNING new.col or old.col
2006-08-12 03:50:27 +00:00
</li><li>In rules, allow VALUES() to contain a mixture of 'old' and 'new'
Add: > o In rules, allow VALUES() to contain a mixture of 'old' and 'new' > references
2006-08-02 13:29:54 +00:00
references
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Done: < o Allow INSERT/UPDATE ... RETURNING new.col or old.col < < This is useful for returning the auto-generated key for an INSERT. < One complication is how to handle rules that run as part of < the insert. < http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php > o -Allow INSERT/UPDATE ... RETURNING new.col or old.col
2006-08-12 03:50:27 +00:00
</li><li>SHOW/SET
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Remove completed items: < * -Allow limits on per-db/role connections 43d41 < * -Prevent dropping user that still owns objects, or auto-drop the objects 49d46 < * -Add the client IP address and port to pg_stat_activity < * -Add session start time and last statement time to pg_stat_activity < * -Add a function that returns the start time of the postmaster 230d224 < o -Allow MIN()/MAX() on arrays < o -Modify array literal representation to handle array index lower bound < of other than one 253d244 < * -Add function to return compressed length of TOAST data values < * -Prevent to_char() on interval from returning meaningless values < < For example, to_char('1 month', 'mon') is meaningless. Basically, < most date-related parameters to to_char() are meaningless for < intervals because interval is not anchored to a date. < < * -Have views on temporary tables exist in the temporary namespace < * -Allow temporary views on non-temporary tables 329d311 < * -Add BETWEEN SYMMETRIC/ASYMMETRIC < * -Add E'' escape string marker so eventually ordinary strings can treat < backslashes literally, for portability < < * -Allow additional tables to be specified in DELETE for joins < < UPDATE already allows this (UPDATE...FROM) but we need similar < functionality in DELETE. It's been agreed that the keyword should < be USING, to avoid anything as confusing as DELETE FROM a FROM b. < 341d313 < * -Allow REINDEX to rebuild all database indexes < * -Add an option to automatically use savepoints for each statement in a < multi-statement transaction. < < When enabled, this would allow errors in multi-statement transactions < to be automatically ignored. < 426d391 < o -Allow FOR UPDATE queries to do NOWAIT locks 473d437 < o -Allow COPY to understand \x as a hex byte < o -Allow COPY to optionally include column headings in the first line < o -Allow COPY FROM ... CSV to interpret newlines and carriage < returns in data 525d485 < o -Have SHOW ALL show descriptions for server-side variables < o -Allow PL/PgSQL's RAISE function to take expressions < < Currently only constants are supported. < < o -Change PL/PgSQL to use palloc() instead of malloc() 545d499 < o -Allow PL/pgSQL EXECUTE query_var INTO record_var; 550d503 < o -Pass arrays natively instead of as text between plperl and postgres 598d550 < o -Add dumping and restoring of LOB comments 638d589 < * -Implement shared row locks and use them in RI triggers 642d592 < * -Allow triggers to be disabled < * -Add two-phase commit < < < * -Prevent inherited tables from expanding temporary subtables of other < sessions < * -Use indexes for MIN() and MAX() < < MIN/MAX queries can already be rewritten as SELECT col FROM tab ORDER < BY col {DESC} LIMIT 1. Completing this item involves doing this < transformation automatically. < < * -Use index to restrict rows returned by multi-key index when used with < non-consecutive keys to reduce heap accesses < < For an index on col1,col2,col3, and a WHERE clause of col1 = 5 and < col3 = 9, spin though the index checking for col1 and col3 matches, < rather than just col1; also called skip-scanning. < < * -Fetch heap pages matching index entries in sequential order < < Rather than randomly accessing heap pages based on index entries, mark < heap pages needing access in a bitmap and do the lookups in sequential < order. Another method would be to sort heap ctids matching the index < before accessing the heap rows. < < * -Allow non-bitmap indexes to be combined by creating bitmaps in memory < < This feature allows separate indexes to be ANDed or ORed together. This < is particularly useful for data warehousing applications that need to < query the database in an many permutations. This feature scans an index < and creates an in-memory bitmap, and allows that bitmap to be combined < with other bitmap created in a similar way. The bitmap can either index < all TIDs, or be lossy, meaning it records just page numbers and each < page tuple has to be checked for validity in a separate pass. < < * -Fix incorrect rtree results due to wrong assumptions about "over" < operator semantics 782d694 < o -Add concurrency to GIST 813d724 < * -Allow multiple blocks to be written to WAL with one write() < * -Consider use of open/fcntl(O_DIRECT) to minimize OS caching, < for WAL writes < < O_DIRECT doesn't have the same media write guarantees as fsync, so it < is in addition to the fsync method, not in place of it. < < * -Cache last known per-tuple offsets to speed long tuple access < * -Allow the size of the buffer cache used by temporary objects to be < specified as a GUC variable < < Larger local buffer cache sizes requires more efficient handling of < local cache lookups. < < * -Improve the background writer < < Allow the background writer to more efficiently write dirty buffers < from the end of the LRU cache and use a clock sweep algorithm to < write other dirty buffers to reduced checkpoint I/O < 897d788 < * -Add a warning when the free space map is too small 917d807 < o -Move into the backend code < * -Make locking of shared data structures more fine-grained < < This requires that more locks be acquired but this would reduce lock < contention, improving concurrency. < < * -Improve SMP performance on i386 machines < < i386-based SMP machines can generate excessive context switching < caused by lock failure in high concurrency situations. This may be < caused by CPU cache line invalidation inefficiencies. < 979d857 < o -Add ability to turn off full page writes < * -Eliminate WAL logging for CREATE TABLE AS when not doing WAL archiving < * -Change WAL to use 32-bit CRC, for performance reasons < < * -Use CHECK constraints to influence optimizer decisions < < CHECK constraints contain information about the distribution of values < within the table. This is also useful for implementing subtables where < a tables content is distributed across several subtables. < 1045d913 < * -ANALYZE should record a pg_statistic entry for an all-NULL column 1099d966 < * -Remove kerberos4 from source tree 1103d969 < * -Make src/port/snprintf.c thread-safe 1118d983 < * -Add C code on Unix to copy directories for use in creating new databases 1133d997 < o -Improve dlerror() reporting string
2005-08-26 18:59:48 +00:00
<li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
ANALYZE, and CLUSTER
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
</li></ul>
<h1><a name="section_8">Referential Integrity</a></h1>
<ul>
<li>Add MATCH PARTIAL referential integrity
</li><li>Change foreign key constraint for array -&gt; element to mean element
in array?
</li><li>Fix problem when cascading referential triggers make changes on
cascaded tables, seeing the tables in an intermediate state
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
</p>
</li><li>Allow DEFERRABLE and end-of-statement UNIQUE constraints?
<p> This would allow UPDATE tab SET col = col + 1 to work if col has
a unique index. Currently, uniqueness checks are done while the
command is being executed, rather than at the end of the statement
or transaction.
<a href="http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html">http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php</a>
Add: > > * Improve referential integrity checks > > http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
2008-03-07 19:18:59 +00:00
</p>
Add URL for: * Optimize referential integrity checks > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php
2008-03-11 14:56:52 +00:00
</li><li>Optimize referential integrity checks
Add: > > * Improve referential integrity checks > > http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
2008-03-07 19:18:59 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php">http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php</a>
Add URL for: * Optimize referential integrity checks > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php
2008-03-11 14:56:52 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php</a>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
</p>
</li></ul>
<h1><a name="section_9">Server-Side Languages</a></h1>
<ul>
<li>PL/pgSQL
Make "trigger" section: > * Referential Integrity > > o Add MATCH PARTIAL referential integrity > o Change foreign key constraint for array -> element to mean element > in array? > o Enforce referential integrity for system tables > > < Referential Integrity < ===================== < < * Add MATCH PARTIAL referential integrity > Triggers > ======== < * Change foreign key constraint for array -> element to mean element < in array? 801d804 < * Enforce referential integrity for system tables
2006-05-22 20:39:23 +00:00
<ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<li>Fix RENAME to work on variables other than OLD/NEW
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php">http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php</a>
</p>
</li><li>Allow function parameters to be passed by name,
get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
</li><li>Allow handling of %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
</li><li>Allow listing of record column names, and access to
record columns via variables, e.g. columns := r.(*),
tval2 := r.(colname)
<p> <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php">http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php</a>
</p>
</li><li>Add support for SCROLL cursors
</li><li>Add support for WITH HOLD cursors
</li><li>Allow row and record variables to be set to NULL constants,
and allow NULL tests on such variables
<p> Because a row is not scalar, do not allow assignment
from NULL-valued scalars.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php</a>
Add for pl/pgsql: o Review handling of MOVE and FETCH http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php
2008-03-11 17:20:47 +00:00
</p>
</li><li>Review handling of MOVE and FETCH
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php">http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php</a>
Add to pl/pgsql: > > o Improve logic of determining if an identifier is a a > variable or column name > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00436.php
2008-03-11 22:31:02 +00:00
</p>
</li><li>Improve logic of determining if an identifier is a a
variable or column name
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00436.php">http://archives.postgresql.org/pgsql-hackers/2007-07/msg00436.php</a>
Add: > o Fix problem when cascading referential triggers make changes on > cascaded tables, seeing the tables in an intermediate state > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
2006-06-14 18:36:57 +00:00
</p>
Make "trigger" section: > * Referential Integrity > > o Add MATCH PARTIAL referential integrity > o Change foreign key constraint for array -> element to mean element > in array? > o Enforce referential integrity for system tables > > < Referential Integrity < ===================== < < * Add MATCH PARTIAL referential integrity > Triggers > ======== < * Change foreign key constraint for array -> element to mean element < in array? 801d804 < * Enforce referential integrity for system tables
2006-05-22 20:39:23 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
</li><li>Other
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<li>Add table function support to pltcl, plpythonu
</li><li>Add support for polymorphic arguments and return types to
languages other than PL/PgSQL
</li><li>Add capability to create and call PROCEDURES
</li><li>Add support for OUT and INOUT parameters to languages other
than PL/PgSQL
</li><li>Add PL/PythonU tracebacks
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php</a>
</p>
</li><li>Allow data to be passed in native language formats, rather
than only text
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php</a>
Add: > o Allow data to be passed in native language formats, rather > than only text > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
2007-05-12 22:06:42 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_10">Clients</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>Have pg_ctl look at PGHOST in case it is a socket directory?
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>Allow pg_ctl to work properly with configuration files located outside
the PGDATA directory
<p> pg_ctl can not read the pid file because it isn't located in the
config directory but in the PGDATA directory. The solution is to
allow pg_ctl to read and understand postgresql.conf to find the
data_directory value.
Add: > > * Add a function like pg_get_indexdef() that report more detailed index > information > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php >
2008-03-07 20:38:59 +00:00
</p>
</li><li>Add a function like pg_get_indexdef() that report more detailed index
information
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php">http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php</a>
Add: > > * Prefix command-line utilities like createuser with 'pg_' > > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
2008-03-11 19:48:17 +00:00
</p>
</li><li>Prefix command-line utilities like createuser with 'pg_'
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>psql
<ul>
<li>Have psql show current values for a sequence
</li><li>Move psql backslash database information into the backend, use
mnemonic commands? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?psql">psql</a>]
<p> This would allow non-psql clients to pull the same information out
of the database as psql.
</p>
Update: < o Fix psql's backslash commands more consistent > o Fix psql's \d commands more consistent
2006-04-22 18:18:24 +00:00
</li><li>Fix psql's \d commands more consistent
Update: o Fix psql's \dn for various schema combinations (Neil) http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
2006-04-22 16:06:44 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php</a>
Update: < o Fix psql's \dn for various schema combinations (Neil) > o Fix psql's backslash commands more consistent 625a626 > http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
2006-04-22 18:17:57 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php</a>
Update: o Fix psql's \dn for various schema combinations (Neil) http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
2006-04-22 16:06:44 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>Consistently display privilege information for all objects in psql
Add: > > o Add auto-expanded mode so expanded output is used if the row > length is wider than the screen width. > > Consider using auto-expanded mode for backslash commands like \df+.
2005-10-25 18:50:56 +00:00
</li><li>Add auto-expanded mode so expanded output is used if the row
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
length is wider than the screen width.
Add: > > o Add auto-expanded mode so expanded output is used if the row > length is wider than the screen width. > > Consider using auto-expanded mode for backslash commands like \df+.
2005-10-25 18:50:56 +00:00
<p> Consider using auto-expanded mode for backslash commands like \df+.
Add: > > o Prevent tab completion of SET TRANSACTION from querying the > database and therefore preventing the transaction isolation > level from being set. > > Currently, SET <tab> causes a database lookup to check all > supported session variables. This query causes problems > because setting the transaction isolation level must be the > first statement of a transaction.
2006-02-01 00:03:09 +00:00
</p>
</li><li>Prevent tab completion of SET TRANSACTION from querying the
database and therefore preventing the transaction isolation
level from being set.
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently SET &lt;tab&gt; causes a database lookup to check all
Add: > > o Prevent tab completion of SET TRANSACTION from querying the > database and therefore preventing the transaction isolation > level from being set. > > Currently, SET <tab> causes a database lookup to check all > supported session variables. This query causes problems > because setting the transaction isolation level must be the > first statement of a transaction.
2006-02-01 00:03:09 +00:00
supported session variables. This query causes problems
because setting the transaction isolation level must be the
first statement of a transaction.
Add: > > o Add \# to list command history like \s, but with line numbers > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php >
2007-02-04 01:50:59 +00:00
</p>
Updated TODO item: > o Add a \set variable to control whether \s displays line numbers > Another option is to add \# which lists line numbers, and > allows command execution. > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
2007-02-05 17:17:13 +00:00
</li><li>Add a \set variable to control whether \s displays line numbers
<p> Another option is to add \# which lists line numbers, and
allows command execution.
</p>
Add: > > o Add \# to list command history like \s, but with line numbers > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php >
2007-02-04 01:50:59 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php</a>
Add: > > o Prevent escape string warnings when object names have > backslashes > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php >
2008-03-06 17:28:22 +00:00
</p>
</li><li>Prevent escape string warnings when object names have
backslashes
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php</a>
Add URL item for psql -c changes: > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php
2007-01-11 04:49:01 +00:00
</p>
Add: > o Have \d show foreign keys that reference a table's primary key > > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php > > o Have \d show child tables that inherit from the specified parent
2008-03-07 00:10:13 +00:00
</li><li>Have \d show foreign keys that reference a table's primary key
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php</a>
</p>
</li><li>Have \d show child tables that inherit from the specified parent
Add: > o Have \l+ show database size, if permissions allow > > Ideally it will not generate an error for invalid permissions >
2008-03-07 15:56:40 +00:00
</li><li>Have \l+ show database size, if permissions allow
<p> Ideally it will not generate an error for invalid permissions
Add psql TODO: < * Include the symbolic SQLSTATE name in verbose error reports < < http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php
2008-03-12 20:50:22 +00:00
</p>
</li><li>Include the symbolic SQLSTATE name in verbose error reports
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php">http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php</a>
Add: > o Have \l+ show database size, if permissions allow > > Ideally it will not generate an error for invalid permissions >
2008-03-07 15:56:40 +00:00
</p>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li></ul>
Add ideas for concurrent pg_dump and pg_restore: < * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-04 01:33:32 +00:00
</li><li>pg_dump / pg_restore
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>%Add dumping of comments on index columns and composite type columns
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Add full object name to the tag field. eg. for operators we need
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
'=(integer, integer)', instead of just '='.
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</li><li>Add pg_dumpall custom format dumps?
Add: > o Allow selection of individual object(s) of all types, not just > tables > o In a selective dump, allow dumping of an object and all its > dependencies
2005-10-11 23:55:10 +00:00
</li><li>Allow selection of individual object(s) of all types, not just
tables
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</li><li>In a selective dump, allow dumping of an object and all its
Add: > o Allow selection of individual object(s) of all types, not just > tables > o In a selective dump, allow dumping of an object and all its > dependencies
2005-10-11 23:55:10 +00:00
dependencies
Add: > o Add options like pg_restore -l and -L to pg_dump
2005-10-12 02:57:42 +00:00
</li><li>Add options like pg_restore -l and -L to pg_dump
Rearrange: < o %Add dumping of comments on composite type columns < o %Add dumping of comments on index columns < o Stop dumping CASCADE on DROP TYPE commands in clean mode > o %Add dumping of comments on index columns and composite type columns 604a603 > o Stop dumping CASCADE on DROP TYPE commands in clean mode
2005-10-12 13:41:08 +00:00
</li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
Add: < > o Allow pg_dump --clean to drop roles that own objects or have > privileges
2005-10-12 13:39:21 +00:00
</li><li>Allow pg_dump --clean to drop roles that own objects or have
privileges
Update COMMENT item: < o Prevent COMMENT ON dbname from issuing a warning when loading < into a database with a different name, perhaps using COMMENT ON < CURRENT DATABASE > o Change pg_dump so that a comment on the dumped database is > applied to the loaded database, even if the database has a > different name. This will require new backend syntax, perhaps > COMMENT ON CURRENT DATABASE.
2007-11-20 00:18:46 +00:00
</li><li>Change pg_dump so that a comment on the dumped database is
applied to the loaded database, even if the database has a
different name. This will require new backend syntax, perhaps
COMMENT ON CURRENT DATABASE.
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Remove unnecessary function pointer abstractions in pg_dump source
code
Add ideas for concurrent pg_dump and pg_restore: < * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-04 01:33:32 +00:00
</li><li>Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
multiple objects simultaneously
<p> The difficulty with this is getting multiple dump processes to
Update pg_dump item: < produce a single dump output file. > produce a single dump output file. It also would require > several sessions to share the same snapshot.
2008-03-04 14:38:38 +00:00
produce a single dump output file. It also would require
several sessions to share the same snapshot.
Add ideas for concurrent pg_dump and pg_restore: < * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-04 01:33:32 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php</a>
</p>
</li><li>Allow pg_restore to utilize multiple CPUs and I/O channels by
restoring multiple objects simultaneously
<p> This might require a pg_restore flag to indicate how many
simultaneous operations should be performed. Only pg_dump's
-Fc format has the necessary dependency information.
Add URL for: o Allow pg_restore to utilize multiple CPUs and I/O channels by restoring multiple objects simultaneously > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php
2008-03-04 01:38:37 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php</a>
Add ideas for concurrent pg_dump and pg_restore: < * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-04 01:33:32 +00:00
</p>
</li><li>To better utilize resources, allow pg_restore to check foreign
keys simultaneously, where possible
</li><li>Allow pg_restore to create all indexes of a table
concurrently, via a single heap scan
<p> This requires a pg_dump -Fc file because that format contains
the required dependency information.
<a href="http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php">http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php</a>
</p>
</li><li>Allow pg_restore to load different parts of the COPY data
simultaneously
Add: > o Prevent pg_dump/pg_restore from being affected by > statement_timeout > > Using psql to restore a pg_dump dump is also affected.
2008-03-11 17:02:33 +00:00
</li><li>Prevent pg_dump/pg_restore from being affected by
statement_timeout
<p> Using psql to restore a pg_dump dump is also affected.
</p>
Add: > > o Remove pre-7.3 pg_dump code that assumes pg_depend does not exit
2008-03-17 22:53:02 +00:00
</li><li>Remove pre-7.3 pg_dump code that assumes pg_depend does not exit
Update wording: < o Allow pre/data/post files when dumping a single object, for < performance reasons > o Allow pre/data/post files when schema and data are dumped > separately, for performance reasons
2008-03-24 14:17:06 +00:00
</li><li>Allow pre/data/post files when schema and data are dumped
separately, for performance reasons
Add to pg_dump TODO: > o Allow pre/data/post files when dumping a single object, for > performance reasons > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php >
2008-03-23 00:32:33 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>ecpg
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Docs
<p> Document differences between ecpg and the SQL standard and
information about the Informix-compatibility module.
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Solve cardinality &gt; 1 for input descriptors / variables?
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Add a semantic check level, e.g. check if a table really exists
</li><li>fix handling of DB attributes that are arrays
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Use backend PREPARE/EXECUTE facility for ecpg where possible
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Implement SQLDA
</li><li>Fix nested C comments
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%sqlwarn[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?6">6</a>] should be 'W' if the PRECISION or SCALE value specified
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Make SET CONNECTION thread-aware, non-standard?
</li><li>Allow multidimensional arrays
Fix markup: < * Add internationalized message strings > o Add internationalized message strings
2005-05-17 00:51:58 +00:00
</li><li>Add internationalized message strings
Update: < o COPY FROM STDIN not implemented because not useful? > o Implement COPY FROM STDIN
2006-08-08 22:39:09 +00:00
</li><li>Implement COPY FROM STDIN
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Add for Win32: > o Check WSACancelBlockingCall() for interrupts (win32intr) >
2006-03-06 15:19:45 +00:00
</li><li>libpq
<ul>
Remove completed TODO items: < * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -Zero umasked bits in conversion from INET cast to CIDR < * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -Make row-wise comparisons work per SQL spec < < Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but < the SQL standard requires it to be processed as a column-by-column < comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
2006-09-19 19:20:00 +00:00
<li>Add PQescapeIdentifierConn()
Add for Win32: > o Check WSACancelBlockingCall() for interrupts (win32intr) >
2006-03-06 15:19:45 +00:00
</li><li>Prevent PQfnumber() from lowercasing unquoted the column name
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
<p> PQfnumber() should never have been doing lowercasing, but
Add batch mode, make new libpq section: < * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
2005-11-16 16:33:44 +00:00
historically it has so we need a way to prevent it
</p>
Add for Win32: > o Check WSACancelBlockingCall() for interrupts (win32intr) >
2006-03-06 15:19:45 +00:00
</li><li>Allow statement results to be automatically batched to the client
Update wording: < Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
<p> Currently all statement results are transferred to the libpq
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
client before libpq makes the results available to the
Add batch mode, make new libpq section: < * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
2005-11-16 16:33:44 +00:00
application. This feature would allow the application to make
Force update.
2005-12-16 18:56:55 +00:00
use of the first result rows while the rest are transferred, or
Add batch mode, make new libpq section: < * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
2005-11-16 16:33:44 +00:00
held on the server waiting for them to be requested by libpq.
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
One complexity is that a statement like SELECT 1/col could error
Add batch mode, make new libpq section: < * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
2005-11-16 16:33:44 +00:00
out mid-way through the result set.
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</p>
Add: > o Consider parsing the -c string into individual queries so each > is run in its own transaction > > o Consider disallowing multiple queries in PQexec() as an > additional barrier to SQL injection attacks
2007-01-06 21:58:22 +00:00
</li><li>Consider disallowing multiple queries in PQexec() as an
additional barrier to SQL injection attacks
Add URL for PQexec() for disallowing multiple queries: > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php
2007-01-11 04:42:02 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php</a>
> o Add PQexecf() that allows complex parameter substitution > > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php
2007-04-02 17:15:39 +00:00
</p>
</li><li>Add PQexecf() that allows complex parameter substitution
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php</a>
Add: > o Add SQLSTATE severity to PGconn return status > > http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php
2008-03-07 17:54:15 +00:00
</p>
</li><li>Add SQLSTATE severity to PGconn return status
<p> <a href="http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php">http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php</a>
Add URL for PQexec() for disallowing multiple queries: > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php
2007-01-11 04:42:02 +00:00
</p>
Add for Win32: > o Check WSACancelBlockingCall() for interrupts (win32intr) >
2006-03-06 15:19:45 +00:00
</li></ul>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_11">Triggers</a></h1>
Add: > * Allow more complex user/database default GUC settings > Currently, ALTER USER and ALTER DATABASE support per-user and > per-database defaults. Consider adding per-user-and-database > defaults so things like search_path can be defaulted for a > specific user connecting to a specific database. > >
2006-09-30 03:55:32 +00:00
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Make "trigger" section: > * Referential Integrity > > o Add MATCH PARTIAL referential integrity > o Change foreign key constraint for array -> element to mean element > in array? > o Enforce referential integrity for system tables > > < Referential Integrity < ===================== < < * Add MATCH PARTIAL referential integrity > Triggers > ======== < * Change foreign key constraint for array -> element to mean element < in array? 801d804 < * Enforce referential integrity for system tables
2006-05-22 20:39:23 +00:00
<li>Add deferred trigger queue file
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> Right now all deferred trigger information is stored in backend
memory. This could exhaust memory for very large trigger queues.
This item involves dumping large queues into files.
Update: < * Allow DEFERRABLE UNIQUE constraints? > * Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. >
2006-08-28 23:20:35 +00:00
</p>
Mark item as complete, add another: < * Allow triggers to be disabled [trigger] > * -Allow triggers to be disabled [trigger] > * Allow triggers to be disabled in only the current session. < Currently the only way to disable triggers is to modify the system < tables. > This is currently possible by starting a multi-statement transaction, > modifying the system tables, performing the desired SQL, restoring the > system tables, and committing the transaction. ALTER TABLE ... > TRIGGER requires a table lock so it is not idea for this usage.
2005-08-23 23:51:18 +00:00
</li><li>Allow triggers to be disabled in only the current session.
<p> This is currently possible by starting a multi-statement transaction,
modifying the system tables, performing the desired SQL, restoring the
system tables, and committing the transaction. ALTER TABLE ...
Fix typo.
2005-08-24 14:24:19 +00:00
TRIGGER requires a table lock so it is not ideal for this usage.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li><li>With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
<p> If the dump is known to be valid, allow foreign keys to be added
without revalidating the data.
</p>
</li><li>Allow statement-level triggers to access modified rows
Add URL. < * Support triggers on columns (Greg Sabino Mullane) > * Support triggers on columns > > See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. >
2006-06-08 15:41:22 +00:00
</li><li>Support triggers on columns
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php</a>
Add URL. < * Support triggers on columns (Greg Sabino Mullane) > * Support triggers on columns > > See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. >
2006-06-08 15:41:22 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Allow AFTER triggers on system tables
<p> System tables are modified in many places in the backend without going
through the executor and therefore not causing triggers to fire. To
complete this item, the functions that modify system tables will have
to fire triggers.
Add: > > * Tighten trigger permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
2007-02-01 04:49:43 +00:00
</p>
</li><li>Tighten trigger permission checks
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php</a>
Add: > > * Allow BEFORE INSERT triggers on views > > http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php
2007-03-25 02:21:19 +00:00
</p>
</li><li>Allow BEFORE INSERT triggers on views
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php">http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php</a>
Add: > * Add ability to trigger on TRUNCATE > > http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php
2008-01-11 16:49:27 +00:00
</p>
</li><li>Add ability to trigger on TRUNCATE
<p> <a href="http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php">http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_12">Indexes</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
<ul>
Move INDEX inheritance out into a separate section: < * Allow inherited tables to inherit index, UNIQUE constraint, and primary < key, foreign key < * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from < inherited table: INSERT INTO inherit_table (unique_index_col) VALUES < (dup) should fail < < The main difficulty with this item is the problem of creating an index < that can span more than one table. < < * Allow SELECT ... FOR UPDATE on inherited tables > * Inheritance > > o Allow inherited tables to inherit indexes, UNIQUE constraints, > and primary/foreign keys > o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs > on inherited table, e.g. INSERT INTO inherit_table > (unique_index_col) VALUES (dup) should fail > > The main difficulty with this item is the problem of > creating an index that can span multiple tables. > > o Allow SELECT ... FOR UPDATE on inherited tables > > >
2007-01-06 20:00:10 +00:00
<li>Add UNIQUE capability to non-btree indexes
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Prevent index uniqueness checks when UPDATE does not modify the column
<p> Uniqueness (index) checks are done when updating a column even if the
column is not modified by the UPDATE.
</p>
</li><li>Allow the creation of on-disk bitmap indexes which can be quickly
combined with other bitmap indexes
<p> Such indexes could be more compact if there are only a few distinct values.
Such indexes can also be compressed. Keeping such indexes updated can be
costly.
Add bitmap index URL: > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
2007-01-20 23:18:38 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php</a>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</p>
</li><li>Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
Add URL for: > > http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php >
2007-02-14 00:47:05 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php">http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php</a>
Add URL for: * Allow accurate statistics to be collected on indexes with more than one column or expression indexes, perhaps using per-index statistics > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php
2007-03-21 00:33:08 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php</a>
Add: > > * Consider increasing the number of default statistics target, and > reduce statistics target overhead > > Also consider having a larger statistics target for indexed columns > and expression indexes
2008-03-11 18:30:50 +00:00
</p>
</li><li>Consider increasing the number of default statistics target, and
reduce statistics target overhead
<p> Also consider having a larger statistics target for indexed columns
and expression indexes
Add URL for: * Consider increasing the number of default statistics target, and reduce statistics target overhead Also consider having a larger statistics target for indexed columns and expression indexes > http://archives.postgresql.org/pgsql-general/2007-05/msg01228.php >
2008-03-11 19:32:03 +00:00
<a href="http://archives.postgresql.org/pgsql-general/2007-05/msg01228.php">http://archives.postgresql.org/pgsql-general/2007-05/msg01228.php</a>
Add another URL for: * Consider increasing the number of default statistics target, and reduce statistics target overhead Also consider having a larger statistics target for indexed columns and expression indexes < > http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php
2008-03-11 19:34:12 +00:00
<a href="http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php">http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php</a>
Add TODO URL for: * Consider increasing the number of default statistics target, and reduce statistics target overhead > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php
2008-03-17 21:09:30 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php</a>
Add URL for: > > http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php >
2007-02-14 00:47:05 +00:00
</p>
Update: < * Consider compressing indexes by storing key prefix values shared by > * Consider compressing indexes by storing key values duplicated in 735a736,737 > > This is difficult because it requires datatype-specific knowledge.
2005-10-07 14:04:19 +00:00
</li><li>Consider compressing indexes by storing key values duplicated in
Add: < > * Consider compressing indexes by storing key prefix values shared by > several rows as a single index entry
2005-10-07 02:43:59 +00:00
several rows as a single index entry
Add URLs for: * Consider compressing indexes by storing key values duplicated in several rows as a single index entry > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php >
2008-03-06 22:09:43 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php</a>
Add URL for: * Consider compressing indexes by storing key values duplicated in several rows as a single index entry > http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
2008-03-06 22:17:41 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php</a>
Add URLs for: * Consider compressing indexes by storing key values duplicated in several rows as a single index entry > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php >
2008-03-06 22:09:43 +00:00
</p>
Add: > > * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY > > This is difficult because you must upgrade to an exclusive table lock > to replace the existing index file. CREATE INDEX CONCURRENTLY does not > have this complication. This would allow index compaction without > downtime.
2007-01-31 03:17:49 +00:00
</li><li>Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
<p> This is difficult because you must upgrade to an exclusive table lock
to replace the existing index file. CREATE INDEX CONCURRENTLY does not
have this complication. This would allow index compaction without
downtime.
Add URL for: * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY > http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
2008-03-12 19:15:25 +00:00
<a href="http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php">http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php</a>
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
</li><li>Allow multiple indexes to be created concurrently, ideally via a
Add ideas for concurrent pg_dump and pg_restore: < * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-04 01:33:32 +00:00
single heap scan, and have pg_restore use it
Add to TODO: > > * Consider sorting entries before inserting into btree index > > http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php
2008-03-25 02:17:17 +00:00
</li><li>Consider sorting entries before inserting into btree index
<p> <a href="http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php">http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php</a>
</p>
Move INDEX inheritance out into a separate section: < * Allow inherited tables to inherit index, UNIQUE constraint, and primary < key, foreign key < * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from < inherited table: INSERT INTO inherit_table (unique_index_col) VALUES < (dup) should fail < < The main difficulty with this item is the problem of creating an index < that can span more than one table. < < * Allow SELECT ... FOR UPDATE on inherited tables > * Inheritance > > o Allow inherited tables to inherit indexes, UNIQUE constraints, > and primary/foreign keys > o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs > on inherited table, e.g. INSERT INTO inherit_table > (unique_index_col) VALUES (dup) should fail > > The main difficulty with this item is the problem of > creating an index that can span multiple tables. > > o Allow SELECT ... FOR UPDATE on inherited tables > > >
2007-01-06 20:00:10 +00:00
</li><li>Inheritance
<ul>
<li>Allow inherited tables to inherit indexes, UNIQUE constraints,
and primary/foreign keys
</li><li>Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
on inherited table, e.g. INSERT INTO inherit_table
(unique_index_col) VALUES (dup) should fail
<p> The main difficulty with this item is the problem of
creating an index that can span multiple tables.
</p>
</li><li>Allow SELECT ... FOR UPDATE on inherited tables
Update wording: < o Require all check constraints to be inherited > o Require all CHECK constraints to be inherited
2008-03-07 01:06:55 +00:00
</li><li>Require all CHECK constraints to be inherited
Add: > > o Require all check constraints to be inherited > > http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
2008-03-07 01:06:36 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php">http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php</a>
Add to TODO: > > o Add checks to prevent a CREATE RULE views on inherited tables > > http://archives.postgresql.org/pgsql-general/2008-02/msg01420.php
2008-03-22 22:06:12 +00:00
</p>
</li><li>Add checks to prevent a CREATE RULE views on inherited tables
<p> <a href="http://archives.postgresql.org/pgsql-general/2008-02/msg01420.php">http://archives.postgresql.org/pgsql-general/2008-02/msg01420.php</a>
Add URL for TODO: o Add checks to prevent a CREATE RULE views on inherited tables > http://archives.postgresql.org/pgsql-general/2008-03/msg00077.php
2008-03-22 22:52:26 +00:00
<a href="http://archives.postgresql.org/pgsql-general/2008-03/msg00077.php">http://archives.postgresql.org/pgsql-general/2008-03/msg00077.php</a>
Add: > > o Require all check constraints to be inherited > > http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
2008-03-07 01:06:36 +00:00
</p>
Move INDEX inheritance out into a separate section: < * Allow inherited tables to inherit index, UNIQUE constraint, and primary < key, foreign key < * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from < inherited table: INSERT INTO inherit_table (unique_index_col) VALUES < (dup) should fail < < The main difficulty with this item is the problem of creating an index < that can span more than one table. < < * Allow SELECT ... FOR UPDATE on inherited tables > * Inheritance > > o Allow inherited tables to inherit indexes, UNIQUE constraints, > and primary/foreign keys > o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs > on inherited table, e.g. INSERT INTO inherit_table > (unique_index_col) VALUES (dup) should fail > > The main difficulty with this item is the problem of > creating an index that can span multiple tables. > > o Allow SELECT ... FOR UPDATE on inherited tables > > >
2007-01-06 20:00:10 +00:00
</li></ul>
More TODO list section restructuring.
2005-07-04 17:43:42 +00:00
</li><li>GIST
<ul>
<li>Add more GIST index support for geometric data types
</li><li>Allow GIST indexes to create certain complex index types, like
digital trees (see Aoki)
</li></ul>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Hash
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</li></ul>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php</a>
</p>
<ul>
<li>Pack hash index buckets onto disk pages more efficiently
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
<p> Currently only one hash bucket can be stored on a page. Ideally
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
several hash buckets could be stored on a single page and greater
granularity used for the hash algorithm.
Mark TODO item "autovacuum on by default" as completed.
2007-01-17 03:43:49 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</p>
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</li><li>Consider sorting hash buckets so entries can be found using a
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
binary search, rather than a linear scan
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</li><li>In hash indexes, consider storing the hash value with or instead
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
of the key itself
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</li><li>Add WAL logging for crash recovery
</li><li>Allow multi-column hash indexes
Done: > o -During index creation, pre-sort the tuples to improve build speed
2008-03-17 01:46:42 +00:00
</li><li>-<em>During index creation, pre-sort the tuples to improve build speed</em>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_13">Fsync</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
<li>Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
<p> Ideally this requires a separate test program that can be run
Update: < at initdb time or optionally later. > at initdb time or optionally later. Consider O_SYNC when > O_DIRECT exists.
2005-12-07 17:29:14 +00:00
at initdb time or optionally later. Consider O_SYNC when
O_DIRECT exists.
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
</p>
Add: > * Add program to test if fsync has a delay compared to non-fsync
2005-06-24 02:07:19 +00:00
</li><li>Add program to test if fsync has a delay compared to non-fsync
Add: > * Consider sorting writes during checkpoint > > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00541.php
2008-03-11 20:04:56 +00:00
</li><li>Consider sorting writes during checkpoint
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg00541.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg00541.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_14">Cache Usage</a></h1>
Update TODO script sample.
2005-04-18 14:44:04 +00:00
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
This item was fixed in a different way, so has been removed: < < * Allow free-behind capability for large sequential scans to avoid < kernel cache spoiling < < Posix_fadvise() can control both sequential/random file caching and < free-behind behavior, but it is unclear how the setting affects other < backends that also have the file open, and the feature is not supported < on all operating systems.
2007-12-12 06:59:56 +00:00
<li>Speed up COUNT(*)
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> We could use a fixed row count and a +/- count to follow MVCC
visibility rules, or a single cached value could be used and
invalidated if anyone modifies the table. Another idea is to
get a count directly from a unique index, but for this to be
faster than a sequential scan it must avoid access to the heap
to obtain tuple visibility information.
Mark TODO item "autovacuum on by default" as completed.
2007-01-17 03:43:49 +00:00
</p>
</li><li>Provide a way to calculate an "estimated COUNT(*)"
<p> Perhaps by using the optimizer's cardinality estimates or random
sampling.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li><li>Allow data to be pulled directly from indexes
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
<p> Currently indexes do not have enough tuple visibility information
to allow data to be pulled from the index without also accessing
the heap. One way to allow this is to set a bit on index tuples
to indicate if a tuple is currently visible to all transactions
when the first valid heap lookup happens. This bit would have to
be cleared when a heap tuple is expired.
Add calcluation of bitmap storage capacity. < be cleared when a heap tuple is expired. Another idea is to maintain < a bitmap of heap pages where all rows are visible to all backends, < and allow index lookups to reference that bitmap to avoid heap < lookups, perhaps the same bitmap we might add someday to determine < which heap pages need vacuuming. > be cleared when a heap tuple is expired. > > Another idea is to maintain a bitmap of heap pages where all rows > are visible to all backends, and allow index lookups to reference > that bitmap to avoid heap lookups, perhaps the same bitmap we might > add someday to determine which heap pages need vacuuming. Frequently > accessed bitmaps would have to be stored in shared memory. One 8k > page of bitmaps could track 512MB of heap pages.
2005-12-02 04:28:19 +00:00
</p>
<p> Another idea is to maintain a bitmap of heap pages where all rows
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
are visible to all backends, and allow index lookups to reference
Add calcluation of bitmap storage capacity. < be cleared when a heap tuple is expired. Another idea is to maintain < a bitmap of heap pages where all rows are visible to all backends, < and allow index lookups to reference that bitmap to avoid heap < lookups, perhaps the same bitmap we might add someday to determine < which heap pages need vacuuming. > be cleared when a heap tuple is expired. > > Another idea is to maintain a bitmap of heap pages where all rows > are visible to all backends, and allow index lookups to reference > that bitmap to avoid heap lookups, perhaps the same bitmap we might > add someday to determine which heap pages need vacuuming. Frequently > accessed bitmaps would have to be stored in shared memory. One 8k > page of bitmaps could track 512MB of heap pages.
2005-12-02 04:28:19 +00:00
that bitmap to avoid heap lookups, perhaps the same bitmap we might
add someday to determine which heap pages need vacuuming. Frequently
accessed bitmaps would have to be stored in shared memory. One 8k
page of bitmaps could track 512MB of heap pages.
Add third idea about pulling data from indexes. > 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. > 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 > modified --- any table change would increment the counter.
2007-08-15 15:53:30 +00:00
</p>
<p> 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.
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
modified --- any table change would increment the counter.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
</li><li>Consider automatic caching of statements at various levels:
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Parsed query tree
</li><li>Query execute plan
</li><li>Query results
</li></ul>
Add: > > * Consider increasing internal areas when shared buffers is increased > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
2006-06-14 22:31:53 +00:00
</li><li>Consider increasing internal areas when shared buffers is increased
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php">http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php</a>
Add: > > * Consider decreasing the amount of memory used by PrivateRefCount > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php >
2007-02-20 23:39:03 +00:00
</p>
</li><li>Consider decreasing the amount of memory used by PrivateRefCount
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php</a>
Add to TODO: > > * Consider allowing higher priority queries to have referenced buffer > cache pages stay in memory longer > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php
2008-03-07 20:01:24 +00:00
</p>
</li><li>Consider allowing higher priority queries to have referenced buffer
cache pages stay in memory longer
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php</a>
Add description for concurrent sequential scans: > One possible implementation is to start sequential scans from the lowest > numbered buffer in the shared cache, and when reaching the end wrap > around to the beginning, rather than always starting sequential scans > at the start of the table.
2005-04-25 01:42:41 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_15">Vacuum</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Improve speed with indexes
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index. > > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
2007-04-02 22:49:03 +00:00
<p> For large table adjustments during VACUUM FULL, it is faster to cluster
or reindex rather than update the index. Also, index updates can bloat
the index.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php</a>
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-30 19:07:20 +00:00
<a href="http://archives.postgresql.org/pgsql-performance/2007-05/msg00296.php">http://archives.postgresql.org/pgsql-performance/2007-05/msg00296.php</a>
Add URL for: * Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index. > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00307.php
2008-03-12 01:48:08 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00307.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00307.php</a>
Add: > > * Create a bitmap of pages that need vacuuming > > Instead of sequentially scanning the entire table, have the background > writer or some other process record pages that have expired rows, then > VACUUM can look at just those pages rather than the entire table. In > the event of a system crash, the bitmap would probably be invalidated.
2005-06-17 02:20:43 +00:00
</p>
Re-order item. > * Auto-fill the free space map by scanning the buffer cache or by > checking pages written by the background writer < * Auto-fill the free space map by scanning the buffer cache or by < checking pages written by the background writer
2005-06-17 19:20:27 +00:00
</li><li>Auto-fill the free space map by scanning the buffer cache or by
checking pages written by the background writer
Add URL for freespace map filling. > > http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php >
2006-06-16 18:37:31 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php">http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php</a>
Add URL to: * Auto-fill the free space map by scanning the buffer cache or by checking pages written by the background writer
2006-06-16 18:38:39 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php</a>
Add URL for freespace map filling. > > http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php >
2006-06-16 18:37:31 +00:00
</p>
Add: > > * Create a bitmap of pages that need vacuuming > > Instead of sequentially scanning the entire table, have the background > writer or some other process record pages that have expired rows, then > VACUUM can look at just those pages rather than the entire table. In > the event of a system crash, the bitmap would probably be invalidated.
2005-06-17 02:20:43 +00:00
</li><li>Create a bitmap of pages that need vacuuming
<p> Instead of sequentially scanning the entire table, have the background
writer or some other process record pages that have expired rows, then
VACUUM can look at just those pages rather than the entire table. In
the event of a system crash, the bitmap would probably be invalidated.
Duplicate: < * Maintain a map of recently-expired rows < < This allows vacuum to target specific pages for possible free space < without requiring a sequential scan. < Update entry: > One complexity is that index entries still have to be vacuumed, and > doing this without an index scan (by using the heap values to find the > index entry) might be slow and unreliable, especially for user-defined > index functions.
2005-09-02 00:49:57 +00:00
One complexity is that index entries still have to be vacuumed, and
doing this without an index scan (by using the heap values to find the
index entry) might be slow and unreliable, especially for user-defined
index functions.
Add URL for dead space map: > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php
2007-01-20 23:08:20 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Add: > * Allow FSM to return free space toward the beginning of the heap file, > in hopes that empty pages at the end can be truncated by VACUUM
2006-03-03 03:13:04 +00:00
</li><li>Allow FSM to return free space toward the beginning of the heap file,
in hopes that empty pages at the end can be truncated by VACUUM
Add: > * Allow FSM page return free space based on table clustering, to assist > in maintaining clustering?
2006-03-04 05:02:03 +00:00
</li><li>Allow FSM page return free space based on table clustering, to assist
in maintaining clustering?
Update: * Improve dead row detection during multi-statement transactions usage
2007-03-26 23:48:43 +00:00
</li><li>Improve dead row detection during multi-statement transactions usage
Add: > * Increase the number of rows recognized as dead during multi-statement > transactions > > http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php >
2007-03-26 23:47:53 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php</a>
Add for VACUUM: > > * Consider a more compact data representation for dead tuples > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php
2008-03-11 18:05:10 +00:00
</p>
</li><li>Consider a more compact data representation for dead tuples
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php">http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php</a>
Add: > * Increase the number of rows recognized as dead during multi-statement > transactions > > http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php >
2007-03-26 23:47:53 +00:00
</p>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</li><li>Auto-vacuum
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
<li>%Issue log message to suggest VACUUM FULL if a table is nearly
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 166c167,171 < * %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. > 225c230 < o %Allow MIN()/MAX() on arrays > o -Allow MIN()/MAX() on arrays 228c233 < o Modify array literal representation to handle array index lower bound > o -Modify array literal representation to handle array index lower bound 235a241 > 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. 240d244 < 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 340a345,347 > > This is like DELETE CASCADE, but truncates. > 381c388 < * 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 < SELECT > o Add ON COMMIT capability to CREATE TABLE AS ... SELECT 427c432 < 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 549a548 > 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. < 565c563 < * Have initdb set DateStyle based on locale? > * Have initdb set the input DateStyle (MDY or DMY) based on locale? 567d564 < * 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? 612c605,606 < o Remove unnecessary abstractions in pg_dump source code > o Remove unnecessary function pointer abstractions in pg_dump source > code < * %Remove CREATE CONSTRAINT TRIGGER < < This was used in older releases to dump referential integrity < constraints. < 682a672,675 > 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. > 748c741 < * Fetch heap pages matching index entries in sequential order > * -Fetch heap pages matching index entries in sequential order 797c790 < 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 806a800,802 > o Add WAL logging for crash recovery > o Allow multi-column hash indexes > 812a809,812 > > Ideally this requires a separate test program that can be run > at initdb time or optionally later. > 867c867 < * 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 919c919,920 < o %Suggest VACUUM FULL if a table is nearly empty > o %Issue log message to suggest VACUUM FULL if a table is nearly > empty? 995d995 < * Add WAL index reliability improvement to non-btree indexes 1045c1045 < * ANALYZE should record a pg_statistic entry for an all-NULL column > * -ANALYZE should record a pg_statistic entry for an all-NULL column 1047a1048,1051 > * Allow constraint_elimination to be automatically performed > > This requires additional code to reduce the performance loss caused by > constraint elimination. 1090c1094 < * 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 1113d1116 < * Fix cross-compiling of time zone database via 'zic' 1130c1133 < o Improve dlerror() reporting string > o -Improve dlerror() reporting string 1132c1135 < o Add support for Unicode > o %Add support for Unicode
2005-08-26 18:52:44 +00:00
empty?
Add items: > o Allow multiple vacuums so large tables do not starve small > tables > > http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php > > o Improve control of auto-vacuum > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
2007-01-19 21:36:07 +00:00
</li><li>Improve control of auto-vacuum
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php</a>
Add: > > o Prevent long-lived temporary tables from causing frozen-xid > advancement starvation > > http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php
2007-09-14 19:02:46 +00:00
</p>
</li><li>Prevent long-lived temporary tables from causing frozen-xid
advancement starvation
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
<p> The problem is that autovacuum cannot vacuum them to set frozen xids;
only the session that created them can do that.
<a href="http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php">http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php</a>
Add item: > o Store per-table autovacuum settings in pg_class.reloptions. > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php
2008-03-07 19:03:39 +00:00
</p>
</li><li>Store per-table autovacuum settings in pg_class.reloptions.
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php</a>
Add: > > > o Prevent autovacuum from running if an old transaction is still > running from the last vacuum > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php >
2008-03-07 20:22:25 +00:00
</p>
</li><li>Prevent autovacuum from running if an old transaction is still
running from the last vacuum
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php</a>
Add items: > o Allow multiple vacuums so large tables do not starve small > tables > > http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php > > o Improve control of auto-vacuum > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
2007-01-19 21:36:07 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_16">Locking</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
No longer needed: < < * Add code to detect an SMP machine and handle spinlocks accordingly < from distributted.net, http://www1.distributed.net/source, < in client/common/cpucheck.cpp < < On SMP machines, it is possible that locks might be released shortly, < while on non-SMP machines, the backend should sleep so the process < holding the lock can complete and release it.
2005-10-12 14:06:46 +00:00
<li>Fix priority ordering of read and write light-weight locks (Neil)
Mark TODO item "autovacuum on by default" as completed.
2007-01-17 03:43:49 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php</a>
Add: > > * Fix problem when multiple subtransactions of the same outer transaction > hold different types of locks, and one subtransaction aborts > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
2007-02-01 04:35:52 +00:00
</p>
</li><li>Fix problem when multiple subtransactions of the same outer transaction
hold different types of locks, and one subtransaction aborts
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php</a>
Add URL for: < > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
2007-02-09 03:39:39 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php</a>
Add URL for: * Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php
2008-03-11 18:01:04 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php</a>
Add: > * Allow UPDATEs on only non-referential integrity columns not to conflict > with referential integrity locks > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php
2007-02-19 20:41:40 +00:00
</p>
</li><li>Allow UPDATEs on only non-referential integrity columns not to conflict
with referential integrity locks
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php</a>
Mark TODO item "autovacuum on by default" as completed.
2007-01-17 03:43:49 +00:00
</p>
Update: < * Add transaction_idle_timeout GUC so locks are not held for long > * Add idle_in_transaction_timeout GUC so locks are not held for long
2007-04-03 04:12:00 +00:00
</li><li>Add idle_in_transaction_timeout GUC so locks are not held for long
Update: < * Add idle_timeout GUC so locks are not held for log periods of time > * Add transaction_idle_timeout GUC so locks are not held for long > periods of time
2007-04-03 02:17:11 +00:00
periods of time
Update item: < * Improve deadlock detection when deleting items from shared buffers > * Improve deadlock detection when a page cleaning lock conflicts > with a shared buffer that is pinned
2008-02-01 02:41:10 +00:00
</li><li>Improve deadlock detection when a page cleaning lock conflicts
with a shared buffer that is pinned
Add: > * Improve deadlock detection when deleting items from shared buffers > > http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php > http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php
2008-01-31 15:05:09 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php">http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php</a>
<a href="http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php">http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php</a>
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_17">Startup Time Improvements</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Add: < * Experiment with multi-threaded backend [thread] > * Experiment with multi-threaded backend for backend creation [thread] 1003a1004,1008 > > * Experiment with multi-threaded backend better resource utilization > > This would allow a single query to make use of multiple CPU's or > multiple I/O channels simultaneously.
2006-04-09 20:24:30 +00:00
<li>Experiment with multi-threaded backend for backend creation [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>]
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> This would prevent the overhead associated with process creation. Most
operating systems have trivial process creation time compared to
Force update.
2005-12-16 18:56:55 +00:00
database startup overhead, but a few operating systems (Win32,
Update threading item: < Solaris) might benefit from threading. > Solaris) might benefit from threading. Also explore the idea of > a single session using multiple threads to execute a query faster.
2005-04-23 21:39:27 +00:00
Solaris) might benefit from threading. Also explore the idea of
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
a single session using multiple threads to execute a statement faster.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_18">Write-Ahead Log</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Eliminate need to write full pages to WAL before page modification [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wal">wal</a>]
Update wording: < Currently, to protect against partial disk page writes, we write the > Currently, to protect against partial disk page writes, we write 877c877 < * Turn off after-change writes if fsync is disabled > * Turn off full page writes if fsync is disabled
2005-07-04 04:06:43 +00:00
<p> Currently, to protect against partial disk page writes, we write
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
full page images to WAL before they are modified so we can correct any
partial page writes during recovery. These pages can also be
eliminated from point-in-time archive files.
</p>
Update: > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
2005-07-07 15:18:26 +00:00
<ul>
Remove completed items: < * -Allow limits on per-db/role connections 43d41 < * -Prevent dropping user that still owns objects, or auto-drop the objects 49d46 < * -Add the client IP address and port to pg_stat_activity < * -Add session start time and last statement time to pg_stat_activity < * -Add a function that returns the start time of the postmaster 230d224 < o -Allow MIN()/MAX() on arrays < o -Modify array literal representation to handle array index lower bound < of other than one 253d244 < * -Add function to return compressed length of TOAST data values < * -Prevent to_char() on interval from returning meaningless values < < For example, to_char('1 month', 'mon') is meaningless. Basically, < most date-related parameters to to_char() are meaningless for < intervals because interval is not anchored to a date. < < * -Have views on temporary tables exist in the temporary namespace < * -Allow temporary views on non-temporary tables 329d311 < * -Add BETWEEN SYMMETRIC/ASYMMETRIC < * -Add E'' escape string marker so eventually ordinary strings can treat < backslashes literally, for portability < < * -Allow additional tables to be specified in DELETE for joins < < UPDATE already allows this (UPDATE...FROM) but we need similar < functionality in DELETE. It's been agreed that the keyword should < be USING, to avoid anything as confusing as DELETE FROM a FROM b. < 341d313 < * -Allow REINDEX to rebuild all database indexes < * -Add an option to automatically use savepoints for each statement in a < multi-statement transaction. < < When enabled, this would allow errors in multi-statement transactions < to be automatically ignored. < 426d391 < o -Allow FOR UPDATE queries to do NOWAIT locks 473d437 < o -Allow COPY to understand \x as a hex byte < o -Allow COPY to optionally include column headings in the first line < o -Allow COPY FROM ... CSV to interpret newlines and carriage < returns in data 525d485 < o -Have SHOW ALL show descriptions for server-side variables < o -Allow PL/PgSQL's RAISE function to take expressions < < Currently only constants are supported. < < o -Change PL/PgSQL to use palloc() instead of malloc() 545d499 < o -Allow PL/pgSQL EXECUTE query_var INTO record_var; 550d503 < o -Pass arrays natively instead of as text between plperl and postgres 598d550 < o -Add dumping and restoring of LOB comments 638d589 < * -Implement shared row locks and use them in RI triggers 642d592 < * -Allow triggers to be disabled < * -Add two-phase commit < < < * -Prevent inherited tables from expanding temporary subtables of other < sessions < * -Use indexes for MIN() and MAX() < < MIN/MAX queries can already be rewritten as SELECT col FROM tab ORDER < BY col {DESC} LIMIT 1. Completing this item involves doing this < transformation automatically. < < * -Use index to restrict rows returned by multi-key index when used with < non-consecutive keys to reduce heap accesses < < For an index on col1,col2,col3, and a WHERE clause of col1 = 5 and < col3 = 9, spin though the index checking for col1 and col3 matches, < rather than just col1; also called skip-scanning. < < * -Fetch heap pages matching index entries in sequential order < < Rather than randomly accessing heap pages based on index entries, mark < heap pages needing access in a bitmap and do the lookups in sequential < order. Another method would be to sort heap ctids matching the index < before accessing the heap rows. < < * -Allow non-bitmap indexes to be combined by creating bitmaps in memory < < This feature allows separate indexes to be ANDed or ORed together. This < is particularly useful for data warehousing applications that need to < query the database in an many permutations. This feature scans an index < and creates an in-memory bitmap, and allows that bitmap to be combined < with other bitmap created in a similar way. The bitmap can either index < all TIDs, or be lossy, meaning it records just page numbers and each < page tuple has to be checked for validity in a separate pass. < < * -Fix incorrect rtree results due to wrong assumptions about "over" < operator semantics 782d694 < o -Add concurrency to GIST 813d724 < * -Allow multiple blocks to be written to WAL with one write() < * -Consider use of open/fcntl(O_DIRECT) to minimize OS caching, < for WAL writes < < O_DIRECT doesn't have the same media write guarantees as fsync, so it < is in addition to the fsync method, not in place of it. < < * -Cache last known per-tuple offsets to speed long tuple access < * -Allow the size of the buffer cache used by temporary objects to be < specified as a GUC variable < < Larger local buffer cache sizes requires more efficient handling of < local cache lookups. < < * -Improve the background writer < < Allow the background writer to more efficiently write dirty buffers < from the end of the LRU cache and use a clock sweep algorithm to < write other dirty buffers to reduced checkpoint I/O < 897d788 < * -Add a warning when the free space map is too small 917d807 < o -Move into the backend code < * -Make locking of shared data structures more fine-grained < < This requires that more locks be acquired but this would reduce lock < contention, improving concurrency. < < * -Improve SMP performance on i386 machines < < i386-based SMP machines can generate excessive context switching < caused by lock failure in high concurrency situations. This may be < caused by CPU cache line invalidation inefficiencies. < 979d857 < o -Add ability to turn off full page writes < * -Eliminate WAL logging for CREATE TABLE AS when not doing WAL archiving < * -Change WAL to use 32-bit CRC, for performance reasons < < * -Use CHECK constraints to influence optimizer decisions < < CHECK constraints contain information about the distribution of values < within the table. This is also useful for implementing subtables where < a tables content is distributed across several subtables. < 1045d913 < * -ANALYZE should record a pg_statistic entry for an all-NULL column 1099d966 < * -Remove kerberos4 from source tree 1103d969 < * -Make src/port/snprintf.c thread-safe 1118d983 < * -Add C code on Unix to copy directories for use in creating new databases 1133d997 < o -Improve dlerror() reporting string
2005-08-26 18:59:48 +00:00
<li>When off, write CRC to WAL and check file system blocks
Update: > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
2005-07-07 15:18:26 +00:00
on recovery
Add detail: > > If CRC check fails during recovery, remember the page in case > a later CRC for that page properly matches. >
2005-07-29 16:05:28 +00:00
<p> If CRC check fails during recovery, remember the page in case
a later CRC for that page properly matches.
</p>
Update: > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
2005-07-07 15:18:26 +00:00
</li><li>Write full pages during file system write and not when
the page is modified in the buffer cache
<p> This allows most full page writes to happen in the background
Update: < writer. > writer. It might cause problems for applying WAL on recovery > into a partially-written page, but later the full page will be > replaced from WAL.
2005-07-07 16:02:06 +00:00
writer. It might cause problems for applying WAL on recovery
into a partially-written page, but later the full page will be
replaced from WAL.
Update: > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
2005-07-07 15:18:26 +00:00
</p>
</li></ul>
Fix typo: < * Allow WAL traffic to be steamed to another server for stand-by > * Allow WAL traffic to be streamed to another server for stand-by
2005-09-20 02:21:29 +00:00
</li><li>Allow WAL traffic to be streamed to another server for stand-by
Add: > * Allow WAL traffic to be steamed to another server for stand-by > replication
2005-09-20 00:11:00 +00:00
replication
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Reduce WAL traffic so only modified values are written rather than
Add URL for: * Reduce WAL traffic so only modified values are written rather than entire rows > > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php >
2007-04-05 02:08:53 +00:00
entire rows
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php</a>
</p>
Patch reverted, not done: > * Allow WAL information to recover corrupted pg_controldata
2006-06-03 02:34:35 +00:00
</li><li>Allow WAL information to recover corrupted pg_controldata
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php</a>
Record location of partial patch : > * Allow WAL information to recover corrupted pg_controldata > > See partially completed patch and additional work required at > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. >
2006-06-03 04:00:01 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Find a way to reduce rotational delay when repeatedly writing
last WAL page
<p> Currently fsync of WAL requires the disk platter to perform a full
rotation to fsync again. One idea is to write the WAL to different
offsets that might reduce the rotational delay.
</p>
Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > 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. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
2006-02-07 02:08:08 +00:00
</li><li>Allow WAL logging to be turned off for a table, but the table
might be dropped or truncated during crash recovery [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
Add: > > * Allow control over which tables are WAL-logged > > Allow tables to bypass WAL writes and just fsync() dirty pages on > commit. To do this, only a single writer can modify the table, and > writes must happen only on new pages. Readers can continue accessing > the table. Another option is to avoid transaction logging entirely > and truncate or drop the table on crash recovery. These should be > implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | > TRUNCATE | STABLE | DEFAULT ]. [wallog]
2006-01-05 16:23:48 +00:00
<p> Allow tables to bypass WAL writes and just fsync() dirty pages on
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
commit. This should be implemented using ALTER TABLE, e.g. ALTER
TABLE PERSISTENCE [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo? DROP | TRUNCATE | DEFAULT "> DROP | TRUNCATE | DEFAULT </a>]. Tables using
non-default logging should not use referential integrity with
Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > 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. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
2006-02-07 02:08:08 +00:00
default-logging tables. A table without dirty buffers during a
crash could perhaps avoid the drop/truncate.
</p>
</li><li>Allow WAL logging to be turned off for a table, but the table would
avoid being truncated/dropped [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
<p> To do this, only a single writer can modify the table, and writes
Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > 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. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
2006-02-07 02:08:08 +00:00
must happen only on new pages so the new pages can be removed during
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
crash recovery. Readers can continue accessing the table. Such
tables probably cannot have indexes. One complexity is the handling
Split up wal-logging items: < * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < commit. To do this, only a single writer can modify the table, and < writes must happen only on new pages. Readers can continue accessing < the table. This would affect COPY, and perhaps INSERT/UPDATE too. < Another option is to avoid transaction logging entirely and truncate < or drop the table on crash recovery. These should be implemented < using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | < STABLE | DEFAULT ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > 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. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
2006-02-07 02:08:08 +00:00
of indexes on TOAST tables.
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
</p>
</li><li>Speed WAL recovery by allowing more than one page to be prefetched
Update TODO description: * Speed WAL recovery by allowing more than one page to be prefetched This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay.
2008-03-18 23:32:57 +00:00
<p> This should be done utilizing the same infrastructure used for
prefetching in general to avoid introducing complex error-prone code
in WAL replay.
Add URLs for : * Speed WAL recovery by allowing more than one page to be prefetched This involves having a separate process that can be told which pages the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <
2008-03-18 03:59:45 +00:00
<a href="http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php">http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php</a>
Add: > * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03 18:45:24 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php</a>
Add to TODO: > > * Improve WAL concurrency by increasing lock granularity > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php >
2008-03-23 00:08:47 +00:00
</p>
</li><li>Improve WAL concurrency by increasing lock granularity
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php</a>
Add to TODO: > > * Be more aggressive about creating WAL files > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php
2008-03-25 00:14:53 +00:00
</p>
</li><li>Be more aggressive about creating WAL files
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php</a>
Add to TODO: > > * Have resource managers report the duration of their status changes > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php
2008-03-25 00:28:54 +00:00
</p>
</li><li>Have resource managers report the duration of their status changes
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php</a>
Add to TODO: > > * Move pgfoundry's xlogdump to /contrib and have it rely more closely > on the WAL backend code > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php >
2008-03-25 00:42:23 +00:00
</p>
</li><li>Move pgfoundry's xlogdump to /contrib and have it rely more closely
on the WAL backend code
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php">http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
</li></ul>
Break out referential integrity and server-side languages into separate TODO categories.
2008-03-06 03:15:52 +00:00
<h1><a name="section_19">Optimizer / Executor</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
Update: < * Add missing rtree optimizer selectivity > * Improve selectivity functions for geometric operators
2005-12-29 16:45:11 +00:00
<li>Improve selectivity functions for geometric operators
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Precompile SQL functions to avoid overhead
</li><li>Create utility to compute accurate random_page_cost value
</li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Update entry: < * Have EXPLAIN ANALYZE highlight poor optimizer estimates > * Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and > actual row counts differ by a specified percentage
2006-12-12 22:31:19 +00:00
</li><li>Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and
actual row counts differ by a specified percentage
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Consider using hash buckets to do DISTINCT, rather than sorting
Merge items: < This would be beneficial when there are few distinct values. > This would be beneficial when there are few distinct values. This is > already used by GROUP BY. 946d946 < * Allow DISTINCT to use hashing like GROUP BY
2005-09-20 20:51:30 +00:00
<p> This would be beneficial when there are few distinct values. This is
already used by GROUP BY.
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
</li><li>Log statements where the optimizer row estimates were dramatically
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
different from the number of rows actually found?
Add: > * Consider compressed annealing to search for query plans > > This might replace GEQO, http://sixdemonbag.org/Djinni.
2006-07-31 23:04:13 +00:00
</li><li>Consider compressed annealing to search for query plans
<p> This might replace GEQO, <a href="http://sixdemonbag.org/Djinni">http://sixdemonbag.org/Djinni</a>.
Add: > > * Improve merge join performance by allowing mark/restore of > tuple sources > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php >
2007-01-09 22:43:31 +00:00
</p>
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Improve merge join performance by allowing mark/restore of
Add: > > * Improve merge join performance by allowing mark/restore of > tuple sources > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php >
2007-01-09 22:43:31 +00:00
tuple sources
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php</a>
Add: > > * Consider using a hash for joining to a large IN (VALUES ...) list > > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php
2008-03-11 18:14:57 +00:00
</p>
</li><li>Consider using a hash for joining to a large IN (VALUES ...) list
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php</a>
Add: > * Consider compressed annealing to search for query plans > > This might replace GEQO, http://sixdemonbag.org/Djinni.
2006-07-31 23:04:13 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Add: * Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
2008-03-11 21:06:10 +00:00
<h1><a name="section_20">Background Writer</a></h1>
<ul>
<li>Consider having the background writer update the transaction status
hint bits before writing out the page
<p> Implementing this requires the background writer to have access to system
catalogs and the transaction status log.
</p>
</li><li>Consider adding buffers the background writer finds reusable to the
free list
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
</p>
</li><li>Automatically tune bgwriter_delay based on activity rather then using a
fixed interval
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
</p>
</li><li>Consider wither increasing BM_MAX_USAGE_COUNT improves performance
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php</a>
</p>
</li><li>Test to see if calling PreallocXlogFiles() from the background writer
will help with WAL segment creation latency
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php">http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php</a>
</p>
</li></ul>
<h1><a name="section_21">Miscellaneous Performance</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Do async I/O for faster random read-ahead of data
<p> Async I/O allows multiple I/O requests to be sent to the disk with
results coming back asynchronously.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php</a>
Add URL for: * Do async I/O for faster random read-ahead of data Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously. > http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php
2008-03-13 01:56:46 +00:00
<a href="http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php">http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php</a>
Add random I/O URL: > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php
2007-12-12 07:06:27 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php</a>
Add URL for: * Do async I/O for faster random read-ahead of data Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously. > http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php
2008-03-23 01:13:38 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php">http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php</a>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</p>
Restructure TODO sections.
2005-07-04 17:00:32 +00:00
</li><li>Use mmap() rather than SYSV shared memory or to write WAL files?
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<p> This would remove the requirement for SYSV SHM but would introduce
portability issues. Anonymous mmap (or mmap to /dev/zero) is required
to prevent I/O overhead.
</p>
</li><li>Consider mmap()'ing files into a backend?
<p> Doing I/O to large tables would consume a lot of address space or
require frequent mapping/unmapping. Extending the file also causes
mapping problems that might require mapping only individual pages,
leading to thousands of mappings. Another problem is that there is no
Add URL for case identifiers. < > http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
2006-11-14 22:26:49 +00:00
way to <u>prevent</u> I/O to disk from the dirty shared buffers so changes
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
could hit disk before WAL is written.
</p>
</li><li>Add a script to ask system configuration questions and tune postgresql.conf
Add items: < * Research storing disk pages with no alignment/padding > * Consider ways of storing rows more compactly on disk > > o Store disk pages with no alignment/padding? > o Reorder physical storage order to reduce padding? > o Support a smaller header for short variable-length fields? > o Reduce the row header size?
2006-09-10 22:20:01 +00:00
</li><li>Consider ways of storing rows more compactly on disk
<ul>
Remove completed 8.3 TODO items: < o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
2007-12-07 17:52:15 +00:00
<li>Reduce the row header size?
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Consider reducing on-disk varlena length from four bytes to
Update TODO: < o Consider reducing on-disk varlena length from four to two < because a heap row cannot be more than 64k in length > o Consider reducing on-disk varlena length from four bytes to > two because a heap row cannot be more than 64k in length
2007-04-13 23:23:22 +00:00
two because a heap row cannot be more than 64k in length
Add items: < * Research storing disk pages with no alignment/padding > * Consider ways of storing rows more compactly on disk > > o Store disk pages with no alignment/padding? > o Reorder physical storage order to reduce padding? > o Support a smaller header for short variable-length fields? > o Reduce the row header size?
2006-09-10 22:20:01 +00:00
</li></ul>
Add: > > * Consider increasing NUM_CLOG_BUFFERS
2007-01-27 02:28:16 +00:00
</li><li>Consider increasing NUM_CLOG_BUFFERS
Add URL for: * Consider increasing NUM_CLOG_BUFFERS > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php >
2008-03-12 01:03:04 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php</a>
Add URL for: * Consider increasing NUM_CLOG_BUFFERS > http://archives.postgresql.org/pgsql-performance/2007-08/msg00024.php
2008-03-12 01:08:32 +00:00
<a href="http://archives.postgresql.org/pgsql-performance/2007-08/msg00024.php">http://archives.postgresql.org/pgsql-performance/2007-08/msg00024.php</a>
Add URL for: * Consider increasing NUM_CLOG_BUFFERS > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php >
2008-03-12 01:03:04 +00:00
</p>
Update wording: < * Consider allowing configuration of TOAST thresholds > * Allow user configuration of TOAST thresholds
2007-02-19 21:08:48 +00:00
</li><li>Allow user configuration of TOAST thresholds
Add: > * Consider allowing configuration of TOAST thresholds > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php >
2007-02-19 21:07:25 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php</a>
Add URL for: > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php
2008-03-12 01:21:25 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php</a>
Add: > > * Allow configuration of backend priorities via the operating system > > Though backend priorities make priority inversion during lock > waits possible, research shows that this is not a huge problem. > http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php
2007-03-27 15:36:40 +00:00
</p>
</li><li>Allow configuration of backend priorities via the operating system
<p> Though backend priorities make priority inversion during lock
waits possible, research shows that this is not a huge problem.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php">http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php</a>
Move item to proper section: < * Experiment with multi-threaded backend better resource utilization < < This would allow a single query to make use of multiple CPU's or < multiple I/O channels simultaneously. One idea is to create a < background reader that can pre-fetch sequential and index scan < pages needed by other backends. This could be expanded to allow < concurrent reads from multiple devices in a partitioned table. < > * Experiment with multi-threaded backend better resource utilization > > This would allow a single query to make use of multiple CPU's or > multiple I/O channels simultaneously. One idea is to create a > background reader that can pre-fetch sequential and index scan > pages needed by other backends. This could be expanded to allow > concurrent reads from multiple devices in a partitioned table.
2007-12-21 21:20:27 +00:00
</p>
Spit items: * Experiment with multi-threaded backend better I/O utilization This would allow a single query to make use of multiple I/O channels simultaneously. One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table. * Experiment with multi-threaded backend better CPU utilization This would allow several CPUs to be used for a single query, such as for sorting or query execution.
2008-03-18 23:35:21 +00:00
</li><li>Experiment with multi-threaded backend better I/O utilization
<p> This would allow a single query to make use of multiple I/O channels
simultaneously. One idea is to create a background reader that can
pre-fetch sequential and index scan pages needed by other backends.
This could be expanded to allow concurrent reads from multiple devices
in a partitioned table.
</p>
</li><li>Experiment with multi-threaded backend better CPU utilization
<p> This would allow several CPUs to be used for a single query, such as
for sorting or query execution.
Add: > > * Consider increasing the minimum allowed number of shared buffers > > http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php >
2008-03-10 14:16:37 +00:00
</p>
</li><li>Consider increasing the minimum allowed number of shared buffers
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php">http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</a>
Add to TODO: > * Expire published xmin for read-only and idle transactions > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00343.php
2008-03-12 20:19:46 +00:00
</p>
</li><li>Expire published xmin for read-only and idle transactions
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00343.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00343.php</a>
Add to TODO: > * Consider if CommandCounterIncrement() can avoid its > AcceptInvalidationMessages() call > > http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php
2008-03-17 22:59:01 +00:00
</p>
</li><li>Consider if CommandCounterIncrement() can avoid its
AcceptInvalidationMessages() call
<p> <a href="http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php">http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php</a>
Add TODO: > > * Improve performance of shared invalidation queue for multiple CPUs > > http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
2008-03-22 01:44:42 +00:00
</p>
</li><li>Improve performance of shared invalidation queue for multiple CPUs
<p> <a href="http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php">http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php</a>
Add to TODO: > > * Consider Cartesian joins when both relations are needed to form an > indexscan qualification for a third relation > > http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php
2008-03-18 00:43:01 +00:00
</p>
</li><li>Consider Cartesian joins when both relations are needed to form an
indexscan qualification for a third relation
<p> <a href="http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php">http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php</a>
Add to TODO: > > * Consider not storing a NULL bitmap on disk if all the NULLs are > trailing > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php > http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php >
2008-03-18 18:40:42 +00:00
</p>
</li><li>Consider not storing a NULL bitmap on disk if all the NULLs are
trailing
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php">http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php</a>
Add: > > * Sort large UPDATE/DELETEs so it is done in heap order > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php
2008-03-23 01:23:10 +00:00
</p>
</li><li>Sort large UPDATE/DELETEs so it is done in heap order
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php</a>
Re-add: > > * Avoid tuple some tuple copying in sort routines > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
2008-03-23 01:26:53 +00:00
</p>
</li><li>Avoid tuple some tuple copying in sort routines
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php</a>
Add: > http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php
2008-03-23 01:30:46 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php">http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php</a>
Add to TODO: > > * SMP scalability improvements > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php
2008-03-24 17:29:35 +00:00
</p>
</li><li>SMP scalability improvements
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php">http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php</a>
Add URL for: * SMP scalability improvements > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php
2008-03-24 17:48:07 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php</a>
Add URL to: * SMP scalability improvements > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php
2008-03-24 17:41:16 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php">http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php</a>
Add to TODO: > > * Research reducing deTOASTing in more places > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php
2008-03-24 18:24:30 +00:00
</p>
</li><li>Research reducing deTOASTing in more places
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php</a>
Add: > * Consider allowing configuration of TOAST thresholds > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php >
2007-02-19 21:07:25 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Add: * Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
2008-03-11 21:06:10 +00:00
<h1><a name="section_22">Source Code</a></h1>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
<ul>
<li>Add use of 'const' for variables in source tree
Change /contrib to contrib for consistency.
2008-01-24 06:23:33 +00:00
</li><li>Move some things from contrib into main tree
Mark "easy" items. Jim C. Nasby
2005-08-24 14:05:37 +00:00
</li><li>%Remove warnings created by -Wcast-align
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Move platform-specific ps status display info from ps_status.c to ports
</li><li>Add optional CRC checksum to heap and index pages
</li><li>Improve documentation to build only interfaces (Marc)
</li><li>Remove or relicense modules that are not under the BSD license, if possible
</li><li>Acquire lock on a relation before building a relcache entry for it
</li><li>Allow cross-compiling by generating the zic database on the target system
Done: > * -Add 'tid != tid ' operator for use in corruption recovery
2006-02-26 21:22:47 +00:00
</li><li>Improve NLS maintenance of libpgport messages linked onto applications
Change /contrib to contrib for consistency.
2008-01-24 06:23:33 +00:00
</li><li>Clean up casting in contrib/isn
Add: > * Clean up casting in /contrib/isn > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php >
2007-02-14 04:24:42 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php</a>
</p>
Add: > * Use UTF8 encoding for NLS messages so all server encodings can > read them properly < o %Add support for Unicode < < To fix this, the data needs to be converted to/from UTF16/UTF8 < so the Win32 wcscoll() can be used, and perhaps other functions < like towupper(). However, UTF8 already works with normal < locales but provides no ordering or character set classes.
2005-09-02 20:11:34 +00:00
</li><li>Use UTF8 encoding for NLS messages so all server encodings can
read them properly
Add: < > * Update Bonjour to work with newer cross-platform SDK
2005-09-16 17:37:10 +00:00
</li><li>Update Bonjour to work with newer cross-platform SDK
Add URL for: * Update Bonjour to work with newer cross-platform SDK > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php >
2007-02-13 18:08:39 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php</a>
Add URL for: * Update Bonjour to work with newer cross-platform SDK > http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
2007-02-13 23:23:11 +00:00
<a href="http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php">http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php</a>
Add URL for: * Update Bonjour to work with newer cross-platform SDK > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php >
2007-02-13 18:08:39 +00:00
</p>
Add: > * Consider detoasting keys before sorting
2006-07-30 01:48:40 +00:00
</li><li>Consider detoasting keys before sorting
Add item: > * Consider GnuTLS if OpenSSL license becomes a problem > > See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php.
2006-05-30 10:21:12 +00:00
</li><li>Consider GnuTLS if OpenSSL license becomes a problem
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php">http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php</a>
Add TLS thread URL: > http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php
2006-12-28 20:51:13 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php</a>
Document issues for SGML and XML: > > * Consider changing documentation from SGML to XML > > http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php >
2006-12-15 03:01:20 +00:00
</p>
Link to summary XML email, rather than thread top: < * Consider changing documentation from SGML to XML > * Consider changing documentation format from SGML to XML < http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php > http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php
2006-12-15 13:28:54 +00:00
</li><li>Consider changing documentation format from SGML to XML
<p> <a href="http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php">http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php</a>
Add URL for strlcpy(): > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php
2006-10-03 00:03:54 +00:00
</p>
Split apart entries, one done now: * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h * Consider making NAMEDATALEN more configurable in future releases
2007-02-06 16:44:14 +00:00
</li><li>Consider making NAMEDATALEN more configurable in future releases
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
</li><li>Update our code to handle 64-bit timezone files to match the zic
Add: > * Update our code to handle 64-bit timezone files to match the zic > source code, which now uses them
2007-02-13 17:03:16 +00:00
source code, which now uses them
Add: > * Have configure choose integer datetimes by default > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
2007-05-12 22:10:40 +00:00
</li><li>Have configure choose integer datetimes by default
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php">http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php</a>
dded to TODO: > > * Support scoped IPv6 addresses > > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php
2007-05-17 23:42:33 +00:00
</p>
</li><li>Support scoped IPv6 addresses
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php">http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php</a>
Add: > * Have configure choose integer datetimes by default > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
2007-05-12 22:10:40 +00:00
</p>
Update: < * Consider allowing 64-bit integers to be passed by value on 64-bit < platforms > * Consider allowing 64-bit integers and floats to be passed by value on > 64-bit platforms > > Also change 32-bit floats (float4) to be passed by value at the same > time. >
2007-05-30 20:26:06 +00:00
</li><li>Consider allowing 64-bit integers and floats to be passed by value on
64-bit platforms
<p> Also change 32-bit floats (float4) to be passed by value at the same
time.
Add: > * Research use of signals and sleep wake ups > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php
2008-03-11 21:13:13 +00:00
</p>
</li><li>Research use of signals and sleep wake ups
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php">http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php</a>
Add: > > * Add automated check for invalid C++ source code constructs > > http://archives.postgresql.org/pgsql-patches/2007-07/msg00056.php
2008-03-11 21:25:02 +00:00
</p>
</li><li>Add automated check for invalid C++ source code constructs
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-07/msg00056.php">http://archives.postgresql.org/pgsql-patches/2007-07/msg00056.php</a>
Add: > > * Consider simplifying how memory context resets handle child contexts > > http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php
2008-03-12 01:35:00 +00:00
</p>
</li><li>Consider simplifying how memory context resets handle child contexts
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php">http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php</a>
Add to TODO: > > * Remove use of MAKE_PTR and MAKE_OFFSET macros > > http://archives.postgresql.org/pgsql-general/2007-08/msg01510.php
2008-03-12 18:32:29 +00:00
</p>
</li><li>Remove use of MAKE_PTR and MAKE_OFFSET macros
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-08/msg01510.php">http://archives.postgresql.org/pgsql-general/2007-08/msg01510.php</a>
Add: > > * Convert single quotes to apostrophes in the PDF documentation > > http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php >
2008-03-21 20:00:53 +00:00
</p>
</li><li>Convert single quotes to apostrophes in the PDF documentation
<p> <a href="http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php">http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php</a>
Add to TODO: > > * Create three versions of libpgport to simplify client code > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php >
2008-03-25 00:02:03 +00:00
</p>
</li><li>Create three versions of libpgport to simplify client code
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php</a>
Add to TODO: > * Remove old-style routines for manipulating tuples > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php
2008-03-25 00:05:10 +00:00
</p>
</li><li>Remove old-style routines for manipulating tuples
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php">http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php</a>
Add to TODO: > > * Improve detection of shared memory segments being used by other > FreeBSD jails > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php
2008-03-25 02:11:22 +00:00
</p>
</li><li>Improve detection of shared memory segments being used by other
FreeBSD jails
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php</a>
Update: < * Consider allowing 64-bit integers to be passed by value on 64-bit < platforms > * Consider allowing 64-bit integers and floats to be passed by value on > 64-bit platforms > > Also change 32-bit floats (float4) to be passed by value at the same > time. >
2007-05-30 20:26:06 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li><li>Win32
<ul>
<li>Remove configure.in check for link failure when cause is found
</li><li>Remove readdir() errno patch when runtime/mingwex/dirent.c rev
1.4 is released
</li><li>Remove psql newline patch when we find out why mingw outputs an
extra newline
</li><li>Allow psql to use readline once non-US code pages work with
backslashes
</li><li>Fix problem with shared memory on the Win32 Terminal Server
Add for Win32 TODO: > o Diagnose problem where shared memory can sometimes not be > attached by postmaster children > > http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php >
2008-03-12 18:33:54 +00:00
</li><li>Diagnose problem where shared memory can sometimes not be
attached by postmaster children
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php">http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php</a>
</p>
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
</li><li>Improve signal handling
<p> <a href="http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php">http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php</a>
Add for Win32 TODO: > > o Convert MSVC build system to remove most batch files > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php
2008-03-12 19:28:03 +00:00
</p>
</li><li>Convert MSVC build system to remove most batch files
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php">http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php</a>
Add: > > o Prevent SSL from sending network packets to avoid interference > with Win32 signal emulation > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php
2008-03-21 19:34:33 +00:00
</p>
</li><li>Prevent SSL from sending network packets to avoid interference
with Win32 signal emulation
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php">http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php</a>
Use simple URL's rather than text and a URL: < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
2006-06-08 16:07:23 +00:00
</p>
Update text: < o Support pgxs > o Support pgxs when using MSVC
2008-03-23 12:36:59 +00:00
</li><li>Support pgxs when using MSVC
Add to Win3 TODO: > > o Fix MSVC NLS support, like for to_char() > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php > http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
2008-03-23 00:14:41 +00:00
</li><li>Fix MSVC NLS support, like for to_char()
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php">http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php</a>
<a href="http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php">http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php</a>
Add to TODO: > > o Fix port/rint.c to be spec-compliant > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php
2008-03-25 02:23:43 +00:00
</p>
</li><li>Fix port/rint.c to be spec-compliant
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php</a>
Add to Win3 TODO: > > o Fix MSVC NLS support, like for to_char() > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php > http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
2008-03-23 00:14:41 +00:00
</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li><li>Wire Protocol Changes
<ul>
<li>Allow dynamic character set handling
</li><li>Add decoded type, length, precision
</li><li>Use compression?
Add URL for case identifiers. < > http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
2006-11-14 22:26:49 +00:00
</li><li>Update clients to use data types, typmod, schema.table.column names
Update wording, query -> statement: < * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
2005-12-12 13:36:36 +00:00
of result sets using new statement protocol
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
</li></ul>
Add: * Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
2008-03-11 21:06:10 +00:00
<h1><a name="section_23">Exotic Features</a></h1>
Move "Exotic Features" to the bottom of TODO.
2006-10-02 14:00:04 +00:00
<ul>
<li>Add pre-parsing phase that converts non-ISO syntax to supported
syntax
<p> This could allow SQL written for other databases to run without
modification.
</p>
</li><li>Allow plug-in modules to emulate features from other databases
Update wording: < * Add Oracle-style packages (Pavel) > * Add features of Oracle-style packages (Pavel)
2008-02-29 14:56:50 +00:00
</li><li>Add features of Oracle-style packages (Pavel)
Add item: > * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
2008-01-29 16:11:19 +00:00
<p> A package would be a schema with session-local variables,
public/private functions, and initialization functions. It
is also possible to implement these capabilities
in any schema and not use a separate "packages"
syntax at all.
Move "Exotic Features" to the bottom of TODO.
2006-10-02 14:00:04 +00:00
</p>
Add item: > * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
2008-01-29 16:11:19 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php</a>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
</p>
Add item: > * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
2008-01-29 16:11:19 +00:00
</li><li>Consider allowing control of upper/lower case folding of unquoted
Move "Exotic Features" to the bottom of TODO.
2006-10-02 14:00:04 +00:00
identifiers
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php">http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php</a>
Add URL for case identifiers. < > http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
2006-11-14 22:26:49 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php</a>
Add item: > * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
2008-01-29 16:11:19 +00:00
</p>
Update wording: < * Add anonymous transactions > * Add autonomous transactions
2008-01-29 16:13:09 +00:00
</li><li>Add autonomous transactions
Add item: > * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
2008-01-29 16:11:19 +00:00
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php</a>
Move "Exotic Features" to the bottom of TODO.
2006-10-02 14:00:04 +00:00
</p>
</li></ul>
Add: * Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
2008-03-11 21:06:10 +00:00
<h1><a name="section_24">Features We Do <u>Not</u> Want</a></h1>
Add TODO items we don't want (Idea from Josh Berkus) > > > Features We Do _Not_ Want > ========================= > > * All backends running as threads in a single process (not want) > > This eliminates the process protection we get from the current setup. > Thread creation is usually the same overhead as process creation on > modern systems, so it seems unwise to use a pure threaded model. > > * Optimizer hints (not want) > > Optimizer hints are used to work around problems in the optimizer. We > would rather have the problems reported and fixed. > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
2006-08-09 16:35:51 +00:00
<ul>
Add "AS" item: < * All backends running as threads in a single process (not want) > * All backends running as threads in a single process (not wanted) < * Optimizer hints (not want) > * Optimizer hints (not wanted) > > * Allow AS in "SELECT col AS label" to be optional (not wanted) > > Because we support postfix operators, it isn't possible to make AS > optional and continue to use bison. > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
2006-08-23 18:32:02 +00:00
<li>All backends running as threads in a single process (not wanted)
Add TODO items we don't want (Idea from Josh Berkus) > > > Features We Do _Not_ Want > ========================= > > * All backends running as threads in a single process (not want) > > This eliminates the process protection we get from the current setup. > Thread creation is usually the same overhead as process creation on > modern systems, so it seems unwise to use a pure threaded model. > > * Optimizer hints (not want) > > Optimizer hints are used to work around problems in the optimizer. We > would rather have the problems reported and fixed. > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
2006-08-09 16:35:51 +00:00
<p> This eliminates the process protection we get from the current setup.
Thread creation is usually the same overhead as process creation on
modern systems, so it seems unwise to use a pure threaded model.
</p>
Add "AS" item: < * All backends running as threads in a single process (not want) > * All backends running as threads in a single process (not wanted) < * Optimizer hints (not want) > * Optimizer hints (not wanted) > > * Allow AS in "SELECT col AS label" to be optional (not wanted) > > Because we support postfix operators, it isn't possible to make AS > optional and continue to use bison. > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
2006-08-23 18:32:02 +00:00
</li><li>Optimizer hints (not wanted)
Add TODO items we don't want (Idea from Josh Berkus) > > > Features We Do _Not_ Want > ========================= > > * All backends running as threads in a single process (not want) > > This eliminates the process protection we get from the current setup. > Thread creation is usually the same overhead as process creation on > modern systems, so it seems unwise to use a pure threaded model. > > * Optimizer hints (not want) > > Optimizer hints are used to work around problems in the optimizer. We > would rather have the problems reported and fixed. > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
2006-08-09 16:35:51 +00:00
<p> Optimizer hints are used to work around problems in the optimizer. We
would rather have the problems reported and fixed.
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php</a>
Add url's for hints: > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php
2006-10-12 21:40:15 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php</a>
Add "AS" item: < * All backends running as threads in a single process (not want) > * All backends running as threads in a single process (not wanted) < * Optimizer hints (not want) > * Optimizer hints (not wanted) > > * Allow AS in "SELECT col AS label" to be optional (not wanted) > > Because we support postfix operators, it isn't possible to make AS > optional and continue to use bison. > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
2006-08-23 18:32:02 +00:00
</p>
<p> Because we support postfix operators, it isn't possible to make AS
optional and continue to use bison.
Add URL for: * Allow AS in "SELECT col AS label" to be optional (not wanted) > http://archives.postgresql.org/pgsql-hackers/2003-04/msg00436.php
2008-01-04 15:58:27 +00:00
<a href="http://archives.postgresql.org/pgsql-hackers/2003-04/msg00436.php">http://archives.postgresql.org/pgsql-hackers/2003-04/msg00436.php</a>
Add: > * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-17 00:07:54 +00:00
</p>
<p> <a href="http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php">http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php</a>
TODO item not wanted: > > * Embedded server (not wanted) > > While PostgreSQL clients runs fine limited-resource environments, the > server requires multiple processes and a stable pool of resources to > run reliabily and efficiently. Stripping down the PostgreSQL server > to run in the same process address space as the client application > would add too much complexity and failure cases.
2006-12-15 15:40:52 +00:00
</p>
</li><li>Embedded server (not wanted)
Fix typo: < While PostgreSQL clients runs fine limited-resource environments, the > While PostgreSQL clients runs fine in limited-resource environments, the
2006-12-17 03:57:07 +00:00
<p> While PostgreSQL clients runs fine in limited-resource environments, the
TODO item not wanted: > > * Embedded server (not wanted) > > While PostgreSQL clients runs fine limited-resource environments, the > server requires multiple processes and a stable pool of resources to > run reliabily and efficiently. Stripping down the PostgreSQL server > to run in the same process address space as the client application > would add too much complexity and failure cases.
2006-12-15 15:40:52 +00:00
server requires multiple processes and a stable pool of resources to
Fix whitespace in TODO.
2007-08-15 15:36:31 +00:00
run reliabily and efficiently. Stripping down the PostgreSQL server
to run in the same process address space as the client application
Remove developers list from TODO list now that we have URLs to reference discussions. < < < --------------------------------------------------------------------------- < < < Developers who have claimed items are: < -------------------------------------- < * Alvaro is Alvaro Herrera <alvherre@dcc.uchile.cl> < * Andrew is Andrew Dunstan <andrew@dunslane.net> < * Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB < * Christopher is Christopher Kings-Lynne <chriskl@familyhealth.com.au> of < Family Health Network < * D'Arcy is D'Arcy J.M. Cain <darcy@druid.net> of The Cain Gang Ltd. < * David is David Fetter <david@fetter.org> < * Fabien is Fabien Coelho <coelho@cri.ensmp.fr> < * Gavin is Gavin Sherry <swm@linuxworld.com.au> of Alcove Systems Engineering < * Greg is Greg Sabino Mullane <greg@turnstep.com> < * Jan is Jan Wieck <JanWieck@Yahoo.com> of Afilias, Inc. < * Joe is Joe Conway <mail@joeconway.com> < * Karel is Karel Zak <zakkr@zf.jcu.cz> < * Magnus is Magnus Hagander <mha@sollentuna.net> < * Marc is Marc Fournier <scrappy@hub.org> of PostgreSQL, Inc. < * Matthew T. O'Connor <matthew@zeut.net> < * Michael is Michael Meskes <meskes@postgresql.org> of Credativ < * Neil is Neil Conway <neilc@samurai.com> < * Oleg is Oleg Bartunov <oleg@sai.msu.su> < * Pavel is Pavel Stehule <pavel.stehule@hotmail.com> < * Peter is Peter Eisentraut <peter_e@gmx.net> < * Philip is Philip Warner <pjw@rhyme.com.au> of Albatross Consulting Pty. Ltd. < * Rod is Rod Taylor <pg@rbt.ca> < * Simon is Simon Riggs <simon@2ndquadrant.com> < * Stephan is Stephan Szabo <sszabo@megazone23.bigpanda.com> < * Tatsuo is Tatsuo Ishii <ishii@sraoss.co.jp> of SRA OSS, Inc. Japan < * Teodor is Teodor Sigaev <teodor@sigaev.ru> < * Tom is Tom Lane <tgl@sss.pgh.pa.us> of Red Hat
2007-01-25 02:50:12 +00:00
would add too much complexity and failure cases.</p>
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</li></ul>
Update TODO list based on 8.3 completed items: < * Allow major upgrades without dump/reload, perhaps using pg_upgrade < [pg_upgrade] < * Check for unreferenced table files created by transactions that were < in-progress when the server terminated abruptly < < http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php < > * Check for unreferenced table files created by transactions that were > in-progress when the server terminated abruptly > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php > < * Support table partitioning that allows a single table to be stored < in subtables that are partitioned based on the primary key or a WHERE < clause < creation of rules for INSERT/UPDATE/DELETE, and constraints for < rapid partition selection. Options could include range and hash > creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints > for rapid partition selection. Options could include range and hash < < * Improve replication solutions < < o Load balancing < < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. < < o Allow replication over unreliable or non-persistent links < < < o Mark change-on-restart-only values in postgresql.conf < All objects in the default database tablespace must have default < tablespace specifications. This is because new databases are < created by copying directories. If you mix default tablespace < tables and tablespace-specified tables in the same directory, < creating a new database from such a mixed directory would create a < new database with tables that had incorrect explicit tablespaces. < To fix this would require modifying pg_class in the newly copied < database, which we don't currently do. > Currently all objects in the default database tablespace must > have default tablespace specifications. This is because new > databases are created by copying directories. If you mix default > tablespace tables and tablespace-specified tables in the same > directory, creating a new database from such a mixed directory > would create a new database with tables that had incorrect > explicit tablespaces. To fix this would require modifying > pg_class in the newly copied database, which we don't currently > do. < < o Allow recovery.conf to allow the same syntax as > o Allow recovery.conf to support the same syntax as < * Allow user-defined types to specify a type modifier at table creation < time < * Allow all data types to cast to and from TEXT < < http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php < < < o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH < o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS < INTERVAL MONTH), and this should return '12 months' > o Add support for year-month syntax, INTERVAL '50-6' YEAR > TO MONTH > o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 > year' AS INTERVAL MONTH), and this should return '12 months' < * Allow MONEY to be cast to/from other numeric data types > * Allow MONEY to be easily cast to/from other numeric data types > < * Allow functions to have a schema search path specified at creation time < * Fix cases where invalid byte encodings are accepted by the database, < but throw an error on SELECT < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php < * Improve logging of prepared statements recovered during startup > * Improve logging of prepared transactions recovered during startup < * Make standard_conforming_strings the default in 8.4? > * Make standard_conforming_strings the default in 8.5? < * Allow the count returned by SELECT, etc to be to represent as an int64 > * Allow the count returned by SELECT, etc to be represented as an int64 < o Use more reliable method for CREATE DATABASE to get a consistent < copy of db? < o Fix transaction restriction checks for CREATE DATABASE and < other commands < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php < currently allowed. > currently allowed. This currently is done if the table is > created inside the same transaction block as the COPY because > no other backends can see the table. < o Add SET PATH for schemas? < < This is basically the same as SET search_path. < o Enforce referential integrity for system tables < o Add Oracle-style packages (Pavel) < < A package would be a schema with session-local variables, < public/private functions, and initialization functions. It < is also possible to implement these capabilities < in all schemas and not use a separate "packages" < syntax at all. < < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php < < o Add single-step debugging of functions < o Allow RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php < http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php < < o Fix problems with RETURN NEXT on tables with < dropped/added columns after function creation < < http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php < < * Make consistent use of long/short command options --- pg_ctl needs < long ones, pg_config doesn't have short ones, postgres doesn't have < enough long ones, etc. < < < < o Consider parsing the -c string into individual queries so each < is run in its own transaction < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php < < < o Remove unnecessary function pointer abstractions in pg_dump source < code > o Remove unnecessary function pointer abstractions in pg_dump source > code < < < o Fix SSL retry to avoid useless repeated connection attempts and < ensuing misleading error messages > < < This is difficult because it requires datatype-specific knowledge. < < * Improve commit_delay handling to reduce fsync() < * %Add an option to sync() before fsync()'ing checkpoint files > < * Reduce lock time during VACUUM FULL by moving tuples with read lock, < then write lock and truncate table < < Moved tuples are invisible to other backends so they don't require a < write lock. However, the read lock promotion to write lock could lead < to deadlock situations. < < * 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. < < < < o Use free-space map information to guide refilling < o Consider logging activity either to the logs or a system view > The problem is that autovacuum cannot vacuum them to set frozen xids; > only the session that created them can do that. < * Add connection pooling < < It is unclear if this should be done inside the backend code or done < by something external like pgpool. The passing of file descriptors to < existing backends is one of the difficulties with a backend approach. < < * Consider reducing memory used for shared buffer reference count < < http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php < < * %Remove memory/file descriptor freeing before ereport(ERROR) < * %Promote debug_query_string into a server-side function current_query() < * Allow ecpg to work with MSVC and BCC < * Add xpath_array() to /contrib/xml2 to return results as an array < * Allow building in directories containing spaces < < This is probably not possible because 'gmake' and other compiler tools < do not fully support quoting of paths with spaces. < < * Fix sgmltools so PDFs can be generated with bookmarks < * Split out libpq pgpass and environment documentation sections to make < it easier for non-developers to find < * Use strlcpy() rather than our StrNCpy() macro < < http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php < < o Re-enable timezone output on log_line_prefix '%t' when a < shorter timezone string is available < * Allow statements across databases or servers with transaction < semantics < < This can be done using dblink and two-phase commit. > * Add Oracle-style packages (Pavel) < * Add the features of 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 > in any schema and not use a separate "packages" > syntax at all. < o Make private objects accessible only to objects in the same schema < o Allow current_schema.objname to access current schema objects < o Add session variables < o Allow nested schemas > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
2007-12-30 03:22:53 +00:00
Add HTML version of TODO to CVS, for web site use.
2005-04-18 12:58:45 +00:00
</body>
</html>
Reference in New Issue Copy Permalink