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 >
2006-09-02 20:31:50 +00:00
< title > PostgreSQL TODO List< / title >
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" >
2006-09-02 20:31:50 +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 / >
2007-02-19 17:58:32 +00:00
Last updated: Mon Feb 19 12:58:25 EST 2007
2006-09-02 20:31:50 +00:00
< / p >
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 > .
2005-04-18 12:58:45 +00:00
< / p >
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 / >
2005-08-24 14:05:37 +00:00
< strong > A percent sign, "%", marks items that are easier to implement.< / strong >
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 / >
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 > .
2005-04-18 12:58:45 +00:00
< / p >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_2" > Administration< / a > < / h1 >
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 > Allow major upgrades without dump/reload, perhaps using pg_upgrade
2005-06-04 23:32:34 +00:00
[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade" > pg_upgrade< / a > ]
2005-05-10 22:26:56 +00:00
< / li > < li > Check for unreferenced table files created by transactions that were
2005-04-18 12:58:45 +00:00
in-progress when the server terminated abruptly
2006-06-08 18:59:01 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php" > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php< / a >
< / p >
2005-06-23 21:28:10 +00:00
< / li > < li > Allow administrators to safely terminate individual sessions either
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.
2006-08-04 01:24:49 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php" > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php< / a >
2005-06-24 21:28:30 +00:00
< / p >
2005-08-24 14:05:37 +00:00
< / li > < li > %Set proper permissions on non-system schemas during db creation
2005-04-18 12:58:45 +00:00
< p > Currently all schemas are owned by the super-user because they are
copied from the template1 database.
< / p >
2005-07-04 17:00:32 +00:00
< / li > < li > 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
2005-09-23 03:06:03 +00:00
< / li > < li > Add function to report the time of the most recent server reload
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?
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.
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.
2006-04-10 21:06:23 +00:00
< / p >
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
creation of rules for INSERT/UPDATE/DELETE, and constraints for
rapid partition selection. Options could include range and hash
partition selection.
< / p >
< / li > < li > Allow auto-selection of partitioned tables for min/max() operations
2006-09-30 03:55:32 +00:00
< / li > < li > Allow more complex user/database default GUC settings
2007-02-18 01:34:35 +00:00
< p > Currently ALTER USER and ALTER DATABASE support per-user and
2006-09-30 03:55:32 +00:00
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.
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 >
2006-09-30 03:55:32 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < li > Improve replication solutions
< ul >
< li > Load balancing
< p > 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.
< / p >
< / li > < li > Allow replication over unreliable or non-persistent links
< / li > < / ul >
2005-07-04 17:00:32 +00:00
< / li > < li > Configuration files
< 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 commenting of variables in postgresql.conf to restore them
2005-07-04 17:00:32 +00:00
to defaults
2005-08-24 13:57:27 +00:00
< p > Currently, if a variable is commented out, it keeps the
previous uncommented value until a server restarted.
2006-09-18 16:24:07 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php" > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php< / a >
2006-02-13 03:55:02 +00:00
< / p >
< / li > < li > Allow pg_hba.conf to specify host names along with IP addresses
< 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.
2005-07-04 17:00:32 +00:00
< / p >
2005-08-24 14:05:37 +00:00
< / li > < li > %Allow postgresql.conf file values to be changed via an SQL
2005-07-31 13:54:52 +00:00
API, perhaps using SET GLOBAL
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
2005-08-26 20:38:57 +00:00
< / li > < li > Mark change-on-restart-only values in postgresql.conf
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
< p > 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.
< / 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 >
2007-01-25 04:38:59 +00:00
< / li > < li > -< em > Add a GUC variable to control the tablespace for temporary objects< / em >
2005-07-04 17:00:32 +00:00
and sort files
< p > It could start with a random tablespace from a supplied list and
cycle through the list.
< / p >
2006-06-09 18:41:57 +00:00
< / li > < li > Allow WAL replay of CREATE TABLESPACE to work when the directory
2005-07-04 17:00:32 +00:00
structure on the recovery computer is different from the original
2006-06-09 18:41:57 +00:00
< / li > < li > Allow per-tablespace quotas
2005-07-04 17:00:32 +00:00
< / li > < / ul >
2005-07-04 17:43:42 +00:00
< / li > < li > Point-In-Time Recovery (PITR)
2005-07-04 17:00:32 +00:00
< ul >
2006-09-26 11:18:29 +00:00
< li > Allow a warm standby system to also allow read-only statements
2005-07-04 17:00:32 +00:00
[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?pitr" > pitr< / a > ]
< p > This is useful for checking PITR recovery.
< / p >
2006-09-26 11:18:29 +00:00
< / li > < li > %Create dump tool for write-ahead logs for use in determining
transaction id for point-in-time recovery
2005-07-04 17:00:32 +00:00
< / li > < li > Allow the PITR process to be debugged and data examined
2007-02-03 22:32:49 +00:00
< / li > < li > Allow recovery.conf to allow the same syntax as
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 >
< / p >
2005-07-04 17:00:32 +00:00
< / li > < / ul >
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_3" > Monitoring< / a > < / h1 >
2005-07-04 17:00:32 +00:00
< ul >
< li > Allow server log information to be output as INSERT statements
< p > This would allow server log information to be easily loaded into
a database for analysis.
< / p >
2007-01-09 21:33:24 +00:00
< / li > < li > -< em > Add ability to monitor the use of temporary sort files< / em >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_4" > Data Types< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2007-01-06 22:24:16 +00:00
< li > -< em > Make 64-bit version of the MONEY data type< / em >
< / li > < li > Add locale-aware MONEY type, and support multiple currencies
< p > < a href = "http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php" > http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php< / a >
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 >
2005-12-02 17:39:44 +00:00
< / li > < li > Change NUMERIC to enforce the maximum precision
2005-06-25 01:32:02 +00:00
< / li > < li > Add NUMERIC division operator that doesn't round?
2006-11-14 22:26:49 +00:00
< p > Currently NUMERIC < u > rounds< / u > the result to the specified precision.
2005-06-25 01:32:02 +00:00
This means division can return a result that multiplied by the
divisor is greater than the dividend, e.g. this returns a value > 10:
< / p >
< / li > < / ul >
< p > SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6;
< / p >
< p > The positive modulus result returned by NUMERICs might be considered< br / >
inaccurate, in one sense.
< / p >
< ul >
2006-08-21 12:20:26 +00:00
< li > Fix data types where equality comparison isn't intuitive, e.g. box
2005-08-27 13:52:07 +00:00
< / li > < li > Allow user-defined types to specify a type modifier at table creation
time
2007-01-06 22:19:46 +00:00
< / li > < li > -< em > Allow user-defined types to accept 'typmod' parameters< / em >
2006-06-14 17:51:55 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php" > http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php< / a >
< a href = "http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php" > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php< / a >
2006-08-09 18:10:34 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php" > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php< / a >
2006-06-16 18:32:07 +00:00
< / p >
< / 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 >
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 >
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 >
2006-06-14 17:51:55 +00:00
< / p >
2007-01-29 21:19:30 +00:00
< / li > < li > -< em > Add Globally/Universally Unique Identifier (GUID/UUID)< / em >
2006-09-18 16:22:32 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php" > http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php< / a >
2007-01-19 18:13:47 +00:00
< a href = "http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php" > http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php< / a >
2006-09-18 16:22:32 +00:00
< / p >
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 >
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 >
2006-08-17 06:45:12 +00:00
< / p >
< / li > < li > Support a data type with specific enumerated values (ENUM)
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php" > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php< / a >
2006-09-14 18:10:38 +00:00
< / p >
< / 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 >
2006-07-29 15:56:32 +00:00
< / p >
2007-02-09 01:29:48 +00:00
< / li > < li > Consider placing all sequences in a single table, or create a system
view
2005-07-04 17:43:42 +00:00
< / li > < li > Dates and Times
2005-04-18 12:58:45 +00:00
< ul >
2006-02-25 16:34:52 +00:00
< li > Allow infinite dates and intervals just like infinite timestamps
2005-07-04 17:43:42 +00:00
< / li > < li > Merge hardwired timezone names with the TZ database; allow either
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 > ]
< p > If the TIMESTAMP value is stored with a time zone name, interval
2005-07-10 05:06:42 +00:00
computations should adjust based on the time zone rules.
2005-07-04 17:43:42 +00:00
< / p >
2005-08-26 20:38:57 +00:00
< / li > < li > Fix SELECT '0.01 years'::interval, '0.01 months'::interval
2005-10-27 02:33:31 +00:00
< / li > < li > Add a GUC variable to allow output of interval values in ISO8601
format
< / li > < li > Improve timestamptz subtraction to be DST-aware
2007-02-18 01:34:35 +00:00
< p > Currently subtracting one date from another that crosses a
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
< / li > < li > Add overflow checking to timestamp and interval arithmetic
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 >
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 >
2007-01-11 04:27:29 +00:00
< / p >
2005-07-04 17:43:42 +00:00
< / li > < li > Add ISO INTERVAL handling
2006-06-16 16:59:30 +00:00
< / li > < / ul >
< / li > < / ul >
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 >
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
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,
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 >
2006-06-16 16:59:30 +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
2005-07-04 17:43:42 +00:00
INTERVAL MONTH), and this should return '12 months'
2006-06-16 16:59:30 +00:00
< / li > < li > Round or truncate values to the requested precision, e.g.
2005-07-04 17:43:42 +00:00
INTERVAL '11 months' AS YEAR should return one or zero
2006-06-16 16:59:30 +00:00
< / li > < li > Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
2005-04-18 12:58:45 +00:00
< ul >
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
2005-04-18 12:58:45 +00:00
coercion can be performed on empty array expressions
2006-08-17 06:48:38 +00:00
< / li > < li > Add support for arrays of domains
< / li > < li > Add support for arrays of complex types
2007-01-30 22:55:12 +00:00
< / li > < li > ARRAY[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?[1,2" > [1,2< / a > ],[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?3,4" > 3,4< / a > ]])[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?1" > 1< / a > ] should return the same values as
ARRAY[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?[1,2" > [1,2< / a > ],[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?3,4" > 3,4< / a > ]])[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?1:1" > 1:1< / a > ];
2006-06-16 16:59:30 +00:00
< / li > < / ul >
< / li > < li > Binary Data
< ul >
< li > Improve vacuum of large objects, like /contrib/vacuumlo?
< / li > < li > Add security checking for large objects
< / li > < li > Auto-delete large objects when referencing row is deleted
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 > /contrib/lo offers this functionality.
< / p >
2006-06-16 16:59:30 +00:00
< / li > < li > Allow read/write into TOAST values like large objects
2005-04-18 12:58:45 +00:00
< p > This requires the TOAST column to be stored EXTERNAL.
2006-06-14 19:32:48 +00:00
< / p >
2006-06-16 16:59:30 +00:00
< / li > < li > Add API for 64-bit large object access
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 >
2005-04-18 12:58:45 +00:00
< / p >
2006-06-16 16:59:30 +00:00
< / li > < / ul >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_5" > Functions< / a > < / h1 >
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
2005-12-17 14:18:33 +00:00
< / li > < li > %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
2006-06-10 23:33:27 +00:00
pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
2006-08-22 03:40:39 +00:00
< p > These would be for application use, not for use by pg_dump.
< / p >
2006-03-03 02:18:09 +00:00
< / li > < li > Allow to_date() and to_timestamp() accept localized month names
2006-03-03 02:38:57 +00:00
< / li > < li > Add missing parameter handling in to_char()
< / li > < / ul >
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php" > http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php< / a >
< / p >
< ul >
< li > Allow functions to have a schema search path specified at creation time
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
accumulation. Such functionality could also be added to EXTRACT.
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') => 65
< / li > < li > to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
< / li > < li > to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
< / li > < li > to_char(INTERVAL '3 years 5 months','MM') => 41
< / li > < / ul >
2007-02-19 17:58:32 +00:00
< / li > < li > -< em > Add ISO day of week format 'ID' to to_char() where Monday = 1< / em >
2007-02-19 17:21:24 +00:00
< / li > < li > -< em > Add a field 'isoyear' to extract(), based on the ISO week< / em >
2007-01-17 03:43:49 +00:00
< / li > < li > Implement inlining of set-returning functions defined in SQL
2006-11-23 05:01:47 +00:00
< / li > < li > Allow SQL-language functions to return results from RETURNING queries
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 >
2007-02-18 01:32:55 +00:00
< / p >
< / li > < li > Allow SQL-language functions to reference parameters by parameter name
2007-02-18 01:34:35 +00:00
< p > Currently SQL-language functions can only refer to dollar parameters,
e.g. $1
2007-02-14 02:49:37 +00:00
< / p >
2007-02-17 02:01:02 +00:00
< / li > < li > Add SPI_gettypmod() to return the typemod for a TupleDesc
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 >
2007-02-01 04:50:58 +00:00
< / p >
2007-02-17 02:01:02 +00:00
< / li > < li > Allow holdable cursors in SPI
2007-02-01 04:50:58 +00:00
< / li > < li > Tighten function permission checks
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 >
2007-01-27 03:25:49 +00:00
< / p >
2005-07-04 17:00:32 +00:00
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_6" > Multi-Language Support< / a > < / h1 >
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
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.
2005-04-18 12:58:45 +00:00
< / p >
2006-08-11 15:53:39 +00:00
< / li > < li > Allow encoding on a per-column basis optionally using the ICU library:
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 > ]
2006-06-08 16:07:23 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php" > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php< / a >
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 >
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 >
2005-04-18 12:58:45 +00:00
< / p >
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 > ]
2005-04-18 12:58:45 +00:00
< / li > < li > Support multiple simultaneous character sets, per SQL92
2005-07-04 17:00:32 +00:00
< / li > < li > Improve UTF8 combined character handling?
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()?
2005-08-21 01:04:45 +00:00
< / li > < li > Fix problems with wrong runtime encoding conversion for NLS message files
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 >
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 >
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 >
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.
2006-09-28 17:43:36 +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 >
2006-06-14 21:10:50 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_7" > Views / Rules< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2006-02-26 21:22:47 +00:00
< li > Automatically create rules on views so they are updateable, per SQL99
2005-04-18 12:58:45 +00:00
< p > We can only auto-create rules for simple views. For more complex
2006-02-26 21:22:47 +00:00
cases users will still have to write rules manually.
2006-06-16 18:50:24 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php" > http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php< / a >
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
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.
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_8" > SQL Commands< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2006-09-03 13:37:38 +00:00
< li > Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
2005-04-18 12:58:45 +00:00
< / li > < li > Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
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
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 >
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
2007-02-18 01:34:35 +00:00
< p > Currently queries prepared via the libpq API are planned on first
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 >
2006-04-27 02:41:36 +00:00
< / li > < li > Invalidate prepared queries, like INSERT, when the table definition
is altered
2007-02-14 04:19:37 +00:00
< / li > < li > Improve logging of prepared statements recovered during startup
< 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 >
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.
2005-06-04 18:12:38 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < li > Add a GUC variable to warn about non-standard SQL usage in queries
2005-12-01 22:07:59 +00:00
< / li > < li > Add SQL-standard MERGE command, typically used to merge two tables
2005-12-01 22:12:35 +00:00
[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?merge" > merge< / a > ]
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
2005-12-01 22:12:35 +00:00
[< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?merge" > merge< / a > ]
2005-11-15 23:08:24 +00:00
< p > To implement this cleanly requires that the table have a unique index
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.
2005-11-15 23:08:24 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < li > Add NOVICE output level for helpful messages like automatic sequence/index
creation
2006-04-25 14:33:41 +00:00
< / li > < li > Add RESET CONNECTION command to reset all session state
2005-04-18 12:58:45 +00:00
< p > This would include resetting of all variables (RESET ALL), dropping of
Update text for RESET CONNECTION:
< all temporary tables, removal of any NOTIFYs, cursors, prepared
< queries(?), currval()s, etc. This could be used for connection pooling.
< We could also change RESET ALL to have this functionality.
> temporary tables, removing any NOTIFYs, cursors, open transactions,
> prepared queries, currval()s, etc. This could be used for connection
> pooling. We could also change RESET ALL to have this functionality.
> The difficult of this features is allowing RESET ALL to not affect
> changes made by the interface driver for its internal use. One idea is
> for this to be a protocol-only feature. Another approach is to notify
> the protocol when a RESET CONNECTION command is used.
2005-06-07 01:59:39 +00:00
temporary tables, removing any NOTIFYs, cursors, open transactions,
prepared queries, currval()s, etc. This could be used for connection
pooling. We could also change RESET ALL to have this functionality.
The difficult of this features is allowing RESET ALL to not affect
2005-06-07 14:12:07 +00:00
changes made by the interface driver for its internal use. One idea
is for this to be a protocol-only feature. Another approach is to
2006-06-08 16:07:23 +00:00
notify the protocol when a RESET CONNECTION command is used.
2006-06-06 16:27:23 +00:00
< a href = "http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php" > http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php< / a >
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 > Add GUC to issue notice about statements that use unjoined tables
2005-07-30 04:05:17 +00:00
< / li > < li > Allow EXPLAIN to identify tables that were skipped because of
2005-08-22 17:35:03 +00:00
constraint_exclusion
2005-07-30 04:05:17 +00:00
< / li > < li > Allow EXPLAIN output to be more easily processed by scripts
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
2006-04-23 04:00:06 +00:00
< / li > < li > Make standard_conforming_strings the default in 8.3?
< 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 >
2005-09-23 21:55:01 +00:00
< / li > < li > Simplify dropping roles that have objects in several databases
2005-11-28 22:21:58 +00:00
< / li > < li > Allow COMMENT ON to accept an expression rather than just a string
2005-12-17 01:48:37 +00:00
< / li > < li > Allow the count returned by SELECT, etc to be to represent as an int64
to allow a higher range of values
2006-02-01 00:07:26 +00:00
< / li > < li > Add SQL99 WITH clause to SELECT
2006-06-09 01:02:22 +00:00
< / li > < li > Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
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 >
2006-07-28 19:00:45 +00:00
< / li > < li > Allow DISTINCT to work in multiple-argument aggregate calls
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
2006-08-25 23:43:46 +00:00
< / li > < li > Implement SQL:2003 window functions
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
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
< / li > < li > Use more reliable method for CREATE DATABASE to get a consistent
copy of db?
2007-01-11 04:48:03 +00:00
< / li > < li > Fix transaction restriction checks for CREATE DATABASE and
other commands
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php< / a >
< / p >
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...)
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 >
2006-07-27 22:01:34 +00:00
< / p >
2005-07-04 17:43:42 +00:00
< / li > < / ul >
2005-04-18 12:58:45 +00:00
< / li > < li > ALTER
< ul >
2005-08-24 14:05:37 +00:00
< li > %Have ALTER TABLE RENAME rename SERIAL sequence names
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
2006-02-12 19:13:19 +00:00
< / li > < li > %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
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 >
2006-06-08 03:17:11 +00:00
< / p >
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
2005-04-18 12:58:45 +00:00
< / li > < li > Allow ALTER TABLESPACE to move to different directories
2005-06-09 03:00:43 +00:00
< / li > < li > Allow databases to be moved to different tablespaces
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
2005-06-09 03:00:43 +00:00
tablespace. Global system tables can never be moved.
2005-04-18 12:58:45 +00:00
< / p >
2006-03-06 17:10:31 +00:00
< / li > < li > Prevent parent tables from altering or dropping constraints
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
2005-10-27 14:07:29 +00:00
< / li > < li > Have ALTER INDEX update the name of a constraint using that index
2005-10-27 14:16:05 +00:00
< / li > < li > Add ALTER TABLE RENAME CONSTRAINT, update index name also
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 >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
< / li > < li > CLUSTER
< ul >
2006-12-17 03:55:21 +00:00
< li > Make CLUSTER preserve recently-dead tuples per MVCC requirements
< / li > < li > Automatically maintain clustering on a table
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
2005-12-16 18:56:55 +00:00
partially filled for easier reorganization. Another idea would
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.
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 >
2005-04-18 12:58:45 +00:00
< / p >
2005-08-24 14:05:37 +00:00
< / li > < li > %Add default clustering to system tables
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 >
< / 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.
< / p >
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
2005-09-16 16:46:09 +00:00
be removed or have its heap and index files truncated. One
2005-09-02 21:23:05 +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
currently allowed.
2005-09-02 21:10:59 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2005-07-04 17:00:32 +00:00
< / li > < li > GRANT/REVOKE
< ul >
< li > Allow column-level privileges
2005-08-24 14:05:37 +00:00
< / li > < li > %Allow GRANT/REVOKE permissions to be applied to all schema objects
2005-08-01 14:05:03 +00:00
with one command
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 >
2006-06-09 18:41:57 +00:00
< / li > < li > Allow GRANT/REVOKE permissions to be inherited by objects based on
2005-07-04 17:00:32 +00:00
schema permissions
2006-06-09 18:41:57 +00:00
< / li > < li > Allow SERIAL sequences to inherit permissions from the base table?
2005-07-04 17:00:32 +00:00
< / li > < / ul >
2005-04-18 12:58:45 +00:00
< / li > < li > CURSOR
< ul >
< li > Allow UPDATE/DELETE WHERE CURRENT OF cursor
< p > This requires using the row ctid to map cursor rows back to the
original heap row. This become more complicated if WITH HOLD cursors
are to be supported because WITH HOLD cursors have a copy of the row
and no FOR UPDATE lock.
< / p >
< / li > < li > Prevent DROP TABLE from dropping a row referenced by its own open
2005-07-04 17:00:32 +00:00
cursor?
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
2006-08-12 03:50:27 +00:00
< / li > < li > In rules, allow VALUES() to contain a mixture of 'old' and 'new'
2006-08-02 13:29:54 +00:00
references
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-08-12 03:50:27 +00:00
< / li > < li > SHOW/SET
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
2005-04-18 12:58:45 +00:00
ANALYZE, and CLUSTER
2005-07-04 17:00:32 +00:00
< / li > < li > Add SET PATH for schemas?
2005-04-18 12:58:45 +00:00
< p > This is basically the same as SET search_path.
< / p >
< / li > < / ul >
2006-05-22 20:39:23 +00:00
< / li > < li > Referential Integrity
< ul >
< li > Add MATCH PARTIAL referential integrity
< / li > < li > Change foreign key constraint for array -> element to mean element
in array?
< / li > < li > Enforce referential integrity for system tables
2006-06-14 18:36:57 +00:00
< / 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 >
2006-08-28 23:21:46 +00:00
< / 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.
2006-08-28 23:22:57 +00:00
< 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 >
2006-09-18 14:56:19 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php" > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php< / a >
2006-06-14 18:36:57 +00:00
< / p >
2006-05-22 20:39:23 +00:00
< / li > < / ul >
2005-07-04 17:43:42 +00:00
< / li > < li > Server-Side Languages
2005-04-18 12:58:45 +00:00
< ul >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< li > PL/pgSQL
< ul >
< li > Fix RENAME to work on variables other than OLD/NEW
2007-01-31 04:23:47 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php" > http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php< / a >
2007-02-01 00:32:45 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php< / a >
2007-02-02 21:34:39 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php< / a >
2007-01-31 04:23:47 +00:00
< / p >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< / li > < li > Allow function parameters to be passed by name,
2006-06-16 04:04:52 +00:00
get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
2006-08-08 19:02:13 +00:00
< / li > < li > Add Oracle-style packages (Pavel)
2006-08-09 14:55:39 +00:00
< p > A package would be a schema with session-local variables,
2006-08-09 02:48:10 +00:00
public/private functions, and initialization functions. It
2006-08-08 22:51:37 +00:00
is also possible to implement these capabilities
in all schemas and not use a separate "packages"
syntax at all.
2006-08-09 14:55:39 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php" > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php< / a >
2006-08-08 19:03:59 +00:00
< / p >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< / 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 MOVE
< / li > < li > Add single-step debugging of functions
2006-06-28 15:39:32 +00:00
< / li > < li > Add support for WITH HOLD and SCROLL cursors
< p > PL/pgSQL cursors should support the same syntax as
backend cursors.
< / p >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< / li > < li > Allow PL/RETURN to return row or record functions
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php" > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php< / a >
2006-06-16 17:44:43 +00:00
< / p >
< / li > < li > Fix problems with RETURN NEXT on tables with
dropped/added columns after function creation
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php" > http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php< / a >
2007-02-17 01:35:41 +00:00
< / p >
< / 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.
2006-06-15 16:02:32 +00:00
< / p >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< / li > < / ul >
< / li > < li > Other
< ul >
< li > Add table function support to pltcl, plpython
< / 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
2006-06-16 18:11:03 +00:00
< / li > < li > Add PL/Python 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 >
2006-06-16 22:08:46 +00:00
< / p >
Clarify dynamic pl/pgsql item and add URLs. Restructure server-side
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< 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
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
2006-06-15 16:54:13 +00:00
< / li > < / ul >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_9" > Clients< / a > < / h1 >
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?
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.
2005-04-18 12:58:45 +00:00
< / p >
2007-01-06 22:18:24 +00:00
< / li > < li > 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.
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 >
2006-04-22 18:18:24 +00:00
< / li > < li > Fix psql's \d commands more consistent
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 >
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 >
2006-04-22 16:06:44 +00:00
< / p >
2005-07-04 17:43:42 +00:00
< / li > < li > Allow psql \pset boolean variables to set to fixed values, rather
than toggle
< / li > < li > Consistently display privilege information for all objects in psql
2005-10-25 18:50:56 +00:00
< / li > < li > Add auto-expanded mode so expanded output is used if the row
length is wider than the screen width.
< p > Consider using auto-expanded mode for backslash commands like \df+.
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.
2007-02-18 01:34:35 +00:00
< p > Currently SET < tab> causes a database lookup to check all
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.
2005-08-26 19:41:18 +00:00
< / p >
2007-01-06 21:58:22 +00:00
< / li > < li > Consider parsing the -c string into individual queries so each
is run in its own transaction
2007-01-11 04:49:01 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php< / a >
2007-02-04 01:50:59 +00:00
< / p >
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 >
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 >
2007-01-11 04:49:01 +00:00
< / p >
2005-07-04 17:43:42 +00:00
< / li > < / ul >
2005-04-18 12:58:45 +00:00
< / li > < li > pg_dump
< 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
2005-08-24 14:05:37 +00:00
< / li > < li > %Add full object name to the tag field. eg. for operators we need
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?
< / li > < li > Remove unnecessary function pointer abstractions in pg_dump source
code
2005-10-11 23:55:10 +00:00
< / li > < li > Allow selection of individual object(s) of all types, not just
tables
< / li > < li > In a selective dump, allow dumping of an object and all its
dependencies
2005-10-12 02:57:42 +00:00
< / li > < li > Add options like pg_restore -l and -L to pg_dump
2005-10-12 13:41:08 +00:00
< / li > < li > Stop dumping CASCADE on DROP TYPE commands in clean mode
2005-10-12 13:39:21 +00:00
< / li > < li > Allow pg_dump --clean to drop roles that own objects or have
privileges
2007-01-25 02:48:06 +00:00
< / li > < li > -< em > Add -f to pg_dumpall< / em >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2005-07-04 17:43:42 +00:00
< / li > < li > ecpg
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 >
2005-07-04 17:00:32 +00:00
< / li > < li > Solve cardinality > 1 for input descriptors / variables?
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
< / li > < li > Use backend PREPARE/EXECUTE facility for ecpg where possible
< / li > < li > Implement SQLDA
< / li > < li > Fix nested C comments
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
2005-04-18 12:58:45 +00:00
< / li > < li > Make SET CONNECTION thread-aware, non-standard?
< / li > < li > Allow multidimensional arrays
2005-05-17 00:51:58 +00:00
< / li > < li > Add internationalized message strings
2006-08-08 22:39:09 +00:00
< / li > < li > Implement COPY FROM STDIN
2005-04-18 12:58:45 +00:00
< / li > < / ul >
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()
2006-03-06 15:19:45 +00:00
< / li > < li > Prevent PQfnumber() from lowercasing unquoted the column name
2005-11-16 16:33:44 +00:00
< p > PQfnumber() should never have been doing lowercasing, but
historically it has so we need a way to prevent it
< / p >
2006-03-06 15:19:45 +00:00
< / li > < li > Allow statement results to be automatically batched to the client
2007-02-18 01:34:35 +00:00
< p > Currently all statement results are transferred to the libpq
2005-11-16 16:33:44 +00:00
client before libpq makes the results available to the
application. This feature would allow the application to make
2005-12-16 18:56:55 +00:00
use of the first result rows while the rest are transferred, or
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
2005-11-16 16:33:44 +00:00
out mid-way through the result set.
2007-01-06 21:58:22 +00:00
< li > Fix SSL retry to avoid useless repeated connection attempts and
2006-10-03 00:00:18 +00:00
ensuing misleading error messages
2007-01-06 21:58:22 +00:00
< / li > < li > Consider disallowing multiple queries in PQexec() as an
additional barrier to SQL injection attacks
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 >
< / p >
2006-03-06 15:19:45 +00:00
< / li > < / ul >
2007-01-06 21:58:22 +00:00
< / p > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_10" > Triggers< / a > < / h1 >
2006-09-30 03:55:32 +00:00
2005-04-18 12:58:45 +00:00
< ul >
2006-05-22 20:39:23 +00:00
< li > Add deferred trigger queue file
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.
2006-08-28 23:20:35 +00:00
< / p >
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 ...
2005-08-24 14:24:19 +00:00
TRIGGER requires a table lock so it is not ideal for this usage.
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
2006-06-08 15:41:22 +00:00
< / li > < li > Support triggers on columns
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 >
2006-06-08 15:41:22 +00:00
< / p >
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.
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 >
2005-04-18 12:58:45 +00:00
< / p >
< / li > < / ul >
2006-09-02 20:31:50 +00:00
< h1 > < a name = "section_11" > Dependency Checking< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2005-12-17 18:07:01 +00:00
< li > Flush cached query plans when the dependent objects change,
when the cardinality of parameters changes dramatically, or
when new ANALYZE statistics are available
2005-12-22 23:05:32 +00:00
< p > A more complex solution would be to save multiple plans for different
cardinality and use the appropriate plan based on the EXECUTE values.
< / p >
2005-04-18 12:58:45 +00:00
< / li > < li > Track dependencies in function bodies and recompile/invalidate
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 > This is particularly important for references to temporary tables
in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
2005-08-26 19:32:43 +00:00
in PL/PgSQL is to use EXECUTE. One complexity is that a function
might itself drop and recreate dependent tables, causing it to
invalidate its own query plan.
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 >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_12" > Indexes< / a > < / h1 >
2005-04-18 12:58:45 +00:00
2005-07-04 17:00:32 +00:00
< ul >
2007-01-06 20:00:10 +00:00
< li > Add UNIQUE capability to non-btree indexes
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.
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 >
2005-07-04 17:00:32 +00:00
< / p >
< / li > < li > Allow use of indexes to search for NULLs
< p > One solution is to create a partial index on an IS NULL expression.
< / p >
< / li > < li > Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
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 >
< / p >
2007-01-09 03:43:32 +00:00
< / li > < li > -< em > Allow the creation of indexes with mixed ascending/descending< / em >
2006-04-09 03:27:06 +00:00
specifiers
2005-10-07 14:04:19 +00:00
< / li > < li > Consider compressing indexes by storing key values duplicated in
2005-10-07 02:43:59 +00:00
several rows as a single index entry
2005-10-07 14:04:19 +00:00
< p > This is difficult because it requires datatype-specific knowledge.
2007-01-31 03:17:49 +00:00
< / p >
< / 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.
2005-10-07 14:04:19 +00:00
< / p >
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
< / li > < / ul >
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 >
2005-07-04 17:00:32 +00:00
< / li > < li > Hash
< 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
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.
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 >
2005-07-04 17:00:32 +00:00
< / p >
< / li > < li > Consider sorting hash buckets so entries can be found using a
binary search, rather than a linear scan
< / li > < li > In hash indexes, consider storing the hash value with or instead
of the key itself
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 WAL logging for crash recovery
< / li > < li > Allow multi-column hash indexes
2005-07-04 17:00:32 +00:00
< / li > < / ul >
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_13" > Fsync< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
< li > Improve commit_delay handling to reduce fsync()
< / li > < 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
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 >
2005-08-24 14:05:37 +00:00
< / li > < li > %Add an option to sync() before fsync()'ing checkpoint files
2005-06-24 02:07:19 +00:00
< / li > < li > Add program to test if fsync has a delay compared to non-fsync
2007-02-02 22:55:08 +00:00
< / li > < li > Reduce checkpoint performance degredation by forcing data to disk
more evenly
2007-02-03 01:59:27 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php" > http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php< / a >
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php" > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php< / a >
2007-02-02 22:55:08 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php< / a >
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_14" > Cache Usage< / a > < / h1 >
2005-04-18 14:44:04 +00:00
2005-04-18 12:58:45 +00:00
< ul >
< li > Allow free-behind capability for large sequential scans, perhaps using
posix_fadvise()
< p > 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.
< / p >
< / li > < li > Speed up COUNT(*)
< 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.
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 >
2005-04-18 12:58:45 +00:00
< / p >
< / li > < li > Allow data to be pulled directly from indexes
2005-04-22 15:40:16 +00:00
< p > Currently indexes do not have enough tuple visibility information
to allow data to be pulled from the index without also accessing
2005-12-01 22:30:43 +00:00
the heap. One way to allow this is to set a bit on index tuples
2005-04-22 15:40:16 +00:00
to indicate if a tuple is currently visible to all transactions
when the first valid heap lookup happens. This bit would have to
2005-12-02 04:28:19 +00:00
be cleared when a heap tuple is expired.
< / p >
< p > 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-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:
2005-04-18 12:58:45 +00:00
< ul >
< li > Parsed query tree
< / li > < li > Query execute plan
< / li > < li > Query results
< / li > < / ul >
< / li > < li > Allow sequential scans to take advantage of other concurrent
2005-12-16 18:56:55 +00:00
sequential scans, also called "Synchronised Scanning"
2005-04-25 01:42:41 +00:00
< p > 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.
2007-02-02 23:05:36 +00:00
< / p >
2007-02-03 23:52:19 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php" > http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php< / a >
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php" > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php< / a >
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php" > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php< / a >
2006-06-14 22:31:53 +00:00
< / p >
< / 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 >
2005-04-25 01:42:41 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_15" > Vacuum< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
< li > Improve speed with indexes
2005-12-16 18:56:55 +00:00
< p > For large table adjustments during VACUUM FULL, it is faster to
2007-01-31 03:07:36 +00:00
reindex rather than update the index. Also, index updates can
bloat the index.
2005-04-18 12:58:45 +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 > Reduce lock time during VACUUM FULL by moving tuples with read lock,
then write lock and truncate table
2005-04-18 12:58:45 +00:00
< p > 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.
2005-06-17 02:20:43 +00:00
< / p >
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
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 >
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 >
2006-06-16 18:37:31 +00:00
< / p >
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.
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.
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 >
2005-04-18 12:58:45 +00:00
< / p >
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
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?
2006-06-16 18:48:42 +00:00
< / li > < li > Consider shrinking expired tuples to just their headers
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php" > http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php< / a >
2007-01-25 22:25:53 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php" > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php< / a >
2006-06-24 23:45:02 +00:00
< / p >
2006-06-24 23:47:58 +00:00
< / li > < li > Allow heap reuse of UPDATEd rows if no indexed columns are changed,
and old and new versions are on the same heap page?
< p > While vacuum handles DELETEs fine, updating of non-indexed columns, like
counters, are difficult for VACUUM to handle efficiently. This method
is possible for same-page updates because a single index row can be
used to point to both old and new values.
2006-06-24 23:45:02 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php" > http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php< / a >
2006-06-29 03:04:59 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php" > http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php< / a >
2006-06-16 18:48:42 +00:00
< / p >
2006-06-25 16:27:41 +00:00
< / li > < li > Reuse index tuples that point to heap tuples that are not visible to
anyone?
2005-04-18 12:58:45 +00:00
< / li > < li > Auto-vacuum
< ul >
2006-07-30 01:48:40 +00:00
< li > Use free-space map information to guide refilling
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 > %Issue log message to suggest VACUUM FULL if a table is nearly
empty?
2005-12-04 04:02:55 +00:00
< / li > < li > Consider logging activity either to the logs or a system view
2007-01-17 03:43:49 +00:00
< / li > < li > -< em > Turn on by default< / em >
2007-01-19 21:36:07 +00:00
< / li > < li > Allow multiple vacuums so large tables do not starve small
tables
< p > < a href = "http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php" > http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php< / a >
< / p >
< / 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 >
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_16" > Locking< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2005-10-12 14:06:46 +00:00
< li > Fix priority ordering of read and write light-weight locks (Neil)
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 >
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 >
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 >
2007-01-17 03:43:49 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_17" > Startup Time Improvements< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
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 > ]
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
2005-12-16 18:56:55 +00:00
database startup overhead, but a few operating systems (Win32,
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.
2006-04-09 20:24:30 +00:00
< / p >
< / li > < li > Experiment with multi-threaded backend better resource utilization
< p > This would allow a single query to make use of multiple CPU's or
2006-04-13 10:50:13 +00:00
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.
2005-04-18 12:58:45 +00:00
< / p >
< / li > < li > Add connection pooling
< p > 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.
< / p >
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_18" > Write-Ahead Log< / a > < / h1 >
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 > ]
2005-07-04 04:06:43 +00:00
< p > Currently, to protect against partial disk page writes, we write
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 >
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
2005-07-07 15:18:26 +00:00
on recovery
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 >
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
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.
2005-07-07 15:18:26 +00:00
< / p >
< / li > < / ul >
2005-09-20 02:21:29 +00:00
< / li > < li > Allow WAL traffic to be streamed to another server for stand-by
2005-09-20 00:11:00 +00:00
replication
2005-04-18 12:58:45 +00:00
< / li > < li > Reduce WAL traffic so only modified values are written rather than
2005-07-04 17:00:32 +00:00
entire rows?
2007-01-06 19:41:23 +00:00
< / li > < li > -< em > Allow the pg_xlog directory location to be specified during initdb< / em >
2005-04-18 12:58:45 +00:00
with a symlink back to the /data location
2006-06-03 02:34:35 +00:00
< / li > < li > Allow WAL information to recover corrupted pg_controldata
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 >
2006-06-03 04:00:01 +00:00
< / p >
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 >
< / li > < li > Allow buffered WAL writes and fsync
< p > Instead of guaranteeing recovery of all committed transactions, this
would provide improved performance by delaying WAL writes and fsync
so an abrupt operating system restart might lose a few seconds of
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
2006-01-05 16:23:48 +00:00
< / 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 > ]
2006-01-05 16:23:48 +00:00
< p > Allow tables to bypass WAL writes and just fsync() dirty pages on
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
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
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 > ]
< p > 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.
2005-04-18 12:58:45 +00:00
< / p >
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_19" > Optimizer / Executor< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
2005-12-29 16:45:11 +00:00
< li > Improve selectivity functions for geometric operators
2005-04-25 15:35:32 +00:00
< / li > < li > Allow ORDER BY ... LIMIT # to select high/low value without sort or
2005-04-25 13:03:37 +00:00
index using a sequential scan for highest/lowest values
2005-04-25 15:35:32 +00:00
< p > Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
2005-04-25 13:03:37 +00:00
all values to return the high/low value. Instead The idea is to do a
sequential scan to find the high/low value, thus avoiding the sort.
2005-04-25 15:35:32 +00:00
MIN/MAX already does this, but not for LIMIT > 1.
2005-04-25 13:03:37 +00:00
< / p >
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
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
2005-04-18 12:58:45 +00:00
< / li > < li > Consider using hash buckets to do DISTINCT, rather than sorting
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.
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
2005-07-04 17:00:32 +00:00
different from the number of rows actually found?
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 > .
2007-01-09 22:43:31 +00:00
< / p >
< / li > < li > Improve merge join performance by allowing mark/restore of
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 >
2006-07-31 23:04:13 +00:00
< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_20" > Miscellaneous Performance< / a > < / h1 >
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.
2006-10-21 17:31:18 +00:00
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php" > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php< / a >
2005-04-18 12:58:45 +00:00
< / p >
2005-07-04 17:00:32 +00:00
< / li > < li > Use mmap() rather than SYSV shared memory or to write WAL files?
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
2006-11-14 22:26:49 +00:00
way to < u > prevent< / u > I/O to disk from the dirty shared buffers so changes
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
Done!
< * Merge xmin/xmax/cmin/cmax back into three header fields
<
< Before subtransactions, there used to be only three fields needed to
< store these four values. This was possible because only the current
< transaction looks at the cmin/cmax values. If the current transaction
< created and expired the row the fields stored where xmin (same as
< xmax), cmin, cmax, and if the transaction was expiring a row from a
< another transaction, the fields stored were xmin (cmin was not
< needed), xmax, and cmax. Such a system worked because a transaction
< could only see rows from another completed transaction. However,
< subtransactions can see rows from outer transactions, and once the
< subtransaction completes, the outer transaction continues, requiring
< the storage of all four fields. With subtransactions, an outer
< transaction can create a row, a subtransaction expire it, and when the
< subtransaction completes, the outer transaction still has to have
< proper visibility of the row's cmin, for example, for cursors.
<
< One possible solution is to create a phantom cid which represents a
< cmin/cmax pair and is stored in local memory. Another idea is to
< store both cmin and cmax only in local memory.
<
> * -Merge xmin/xmax/cmin/cmax back into three header fields
2007-02-09 03:37:45 +00:00
< / li > < li > -< em > Merge xmin/xmax/cmin/cmax back into three header fields< / em >
2006-09-10 22:20:01 +00:00
< / li > < li > Consider ways of storing rows more compactly on disk
< ul >
2006-09-16 22:06:54 +00:00
< li > Support a smaller header for short variable-length fields?
< p > One idea is to create zero-or-one-byte-header versions
of varlena data types. In involves setting the high-bit and
0-127 length in the single-byte header, or clear the high bit
and store the 7-bit ASCII value in the rest of the byte.
The small-header versions have no alignment requirements.
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php" > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php< / a >
2006-09-14 17:11:51 +00:00
< / p >
2006-09-10 22:20:01 +00:00
< / li > < li > Reduce the row header size?
2007-02-16 22:20:02 +00:00
< / li > < li > Consider reducing on-disk varlena length from four to two
because a heap row cannot be more than 64k in length
2006-09-10 22:20:01 +00:00
< / li > < / ul >
2007-01-27 02:28:16 +00:00
< / li > < li > Consider increasing NUM_CLOG_BUFFERS
2007-01-27 02:29:32 +00:00
< / li > < li > Consider having the background writer update the transaction status
hint bits before writing out the page
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_21" > Source Code< / a > < / h1 >
2005-04-18 12:58:45 +00:00
< ul >
< li > Add use of 'const' for variables in source tree
< / li > < li > Move some things from /contrib into main tree
2005-08-24 14:05:37 +00:00
< / li > < li > %Remove warnings created by -Wcast-align
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
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 > %Remove memory/file descriptor freeing before ereport(ERROR)
2005-04-18 12:58:45 +00:00
< / li > < li > Acquire lock on a relation before building a relcache entry for it
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 > %Promote debug_query_string into a server-side function current_query()
2005-04-18 12:58:45 +00:00
< / li > < li > Allow cross-compiling by generating the zic database on the target system
2006-02-26 21:22:47 +00:00
< / li > < li > Improve NLS maintenance of libpgport messages linked onto applications
2005-04-18 12:58:45 +00:00
< / li > < li > Allow ecpg to work with MSVC and BCC
< / li > < li > Add xpath_array() to /contrib/xml2 to return results as an array
2007-02-14 04:24:42 +00:00
< / li > < li > Clean up casting in /contrib/isn
< 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 >
2005-04-18 12:58:45 +00:00
< / li > < li > Allow building in directories containing spaces
< p > This is probably not possible because 'gmake' and other compiler tools
do not fully support quoting of paths with spaces.
< / p >
2005-05-10 03:21:58 +00:00
< / li > < li > Fix sgmltools so PDFs can be generated with bookmarks
2005-09-02 20:11:34 +00:00
< / li > < li > Use UTF8 encoding for NLS messages so all server encodings can
read them properly
2005-09-16 17:37:10 +00:00
< / li > < li > Update Bonjour to work with newer cross-platform SDK
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 >
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 >
2007-02-13 18:08:39 +00:00
< / p >
2006-02-28 19:48:03 +00:00
< / li > < li > Split out libpq pgpass and environment documentation sections to make
it easier for non-developers to find
2006-07-30 01:48:40 +00:00
< / li > < li > Consider detoasting keys before sorting
2006-05-30 10:21:12 +00:00
< / li > < li > Consider GnuTLS if OpenSSL license becomes a problem
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 >
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 >
2006-03-02 18:18:00 +00:00
< / p >
2006-10-02 23:26:02 +00:00
< / li > < li > Use strlcpy() rather than our StrNCpy() macro
2006-10-03 00:03:54 +00:00
< p > < a href = "http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php" > http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php< / a >
2006-12-15 03:01:20 +00:00
< / p >
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 >
2006-10-03 00:03:54 +00:00
< / p >
2007-02-06 16:44:14 +00:00
< / li > < li > -< em > Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h< / em >
< / li > < li > Consider making NAMEDATALEN more configurable in future releases
2007-02-13 17:03:16 +00:00
< / li > < li > Update our code to handle 64-bit timezone files to match the zic
source code, which now uses them
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 > Re-enable timezone output on log_line_prefix '%t' when a
shorter timezone string is available
< / li > < li > Fix problem with shared memory on the Win32 Terminal Server
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 >
< / p >
2007-02-19 16:36:17 +00:00
< / li > < li > -< em > Add long file support for binary pg_dump output< / em >
2006-06-14 18:39:18 +00:00
< / li > < li > Check WSACancelBlockingCall() for interrupts [< a href = "http://momjian.postgresql.org/cgi-bin/pgtodo?win32intr" > win32intr< / a > ]
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?
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
2005-04-18 12:58:45 +00:00
< / li > < / ul >
< / li > < / ul >
2006-10-02 14:00:04 +00:00
< h1 > < a name = "section_22" > Exotic Features< / a > < / h1 >
< 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
< / li > < li > SQL*Net listener that makes PostgreSQL appear as an Oracle database
to clients
< / li > < li > Allow statements across databases or servers with transaction
semantics
< p > This can be done using dblink and two-phase commit.
< / p >
< / li > < li > Add the features of packages
< ul >
< li > Make private objects accessible only to objects in the same schema
< / li > < li > Allow current_schema.objname to access current schema objects
< / li > < li > Add session variables
< / li > < li > Allow nested schemas
< / li > < / ul >
< / li > < li > Consider allowing control of upper/lower case folding of unquoted
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 >
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 >
2006-10-02 14:00:04 +00:00
< / p >
< / li > < / ul >
2006-11-14 22:26:49 +00:00
< h1 > < a name = "section_23" > Features We Do < u > Not< / u > Want< / a > < / h1 >
2006-08-09 16:35:51 +00:00
< ul >
2006-08-23 18:32:02 +00:00
< li > All backends running as threads in a single process (not wanted)
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 >
2006-08-23 18:32:02 +00:00
< / li > < li > Optimizer hints (not wanted)
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.
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php" > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php< / a >
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 >
2006-08-23 18:32:02 +00:00
< / p >
< / li > < li > Allow AS in "SELECT col AS label" to be optional (not wanted)
< p > Because we support postfix operators, it isn't possible to make AS
optional and continue to use bison.
< a href = "http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php" > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php< / a >
2006-12-15 15:40:52 +00:00
< / p >
< / li > < li > Embedded server (not wanted)
2006-12-17 03:57:07 +00:00
< p > While PostgreSQL clients runs fine in limited-resource environments, the
2006-12-15 15:40:52 +00:00
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
2007-01-25 02:50:12 +00:00
would add too much complexity and failure cases.< / p >
2005-04-18 12:58:45 +00:00
< / li > < / ul >
2007-01-06 21:58:22 +00:00
< / li > < / ul > < / li > < / ul >
2005-04-18 12:58:45 +00:00
< / body >
< / html >
