2005-04-18 22:42:35 +08:00
|
|
|
PostgreSQL TODO List
|
|
|
|
|
====================
|
2006-06-19 03:34:00 +08:00
|
|
|
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
2007-09-29 05:32:29 +08:00
|
|
|
Last updated: Fri Sep 28 17:32:23 EDT 2007
|
1996-08-19 06:14:33 +08:00
|
|
|
|
2005-04-22 21:38:19 +08:00
|
|
|
The most recent version of this document can be viewed at
|
|
|
|
|
http://www.postgresql.org/docs/faqs.TODO.html.
|
1996-10-04 23:15:24 +08:00
|
|
|
|
2006-09-20 03:20:21 +08:00
|
|
|
#A hyphen, "-", marks changes that will appear in the upcoming 8.3 release.#
|
2005-08-24 22:05:37 +08:00
|
|
|
#A percent sign, "%", marks items that are easier to implement.#
|
2004-11-30 13:03:47 +08:00
|
|
|
|
|
|
|
|
Bracketed items, "[]", have more detail.
|
|
|
|
|
|
|
|
|
|
This list contains all known PostgreSQL bugs and feature requests. If
|
2004-11-30 13:06:33 +08:00
|
|
|
you would like to work on an item, please read the Developer's FAQ
|
2007-01-20 10:18:37 +08:00
|
|
|
first. There is also a developer's wiki at
|
|
|
|
|
http://developer.postgresql.org.
|
2003-10-09 05:44:06 +08:00
|
|
|
|
1999-06-07 10:42:07 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Administration
|
|
|
|
|
==============
|
2002-01-23 05:55:06 +08:00
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
* Allow major upgrades without dump/reload, perhaps using pg_upgrade
|
2005-06-05 07:32:34 +08:00
|
|
|
[pg_upgrade]
|
2005-05-11 06:26:56 +08:00
|
|
|
* Check for unreferenced table files created by transactions that were
|
2004-06-14 21:44:00 +08:00
|
|
|
in-progress when the server terminated abruptly
|
2006-06-09 02:59:01 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php
|
|
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Allow administrators to safely terminate individual sessions either
|
2007-08-28 11:00:36 +08:00
|
|
|
via an SQL function or SIGTERM
|
2004-08-01 13:15:58 +08:00
|
|
|
|
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-27 02:52:44 +08:00
|
|
|
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.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-08-04 09:24:49 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2007-04-18 04:47:55 +08:00
|
|
|
* Set proper permissions on non-system schemas during db creation
|
2004-10-18 10:56:42 +08:00
|
|
|
|
2007-04-18 04:50:34 +08:00
|
|
|
Currently all schemas are owned by the super-user because they are copied
|
|
|
|
|
from the template1 database. However, since all objects are inherited
|
|
|
|
|
from the template database, it is not clear that setting schemas to the db
|
|
|
|
|
owner is correct.
|
2004-10-18 10:56:42 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* 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 11:06:03 +08:00
|
|
|
* Add function to report the time of the most recent server reload
|
2006-02-02 01:32:45 +08:00
|
|
|
* 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-11 05:06:23 +08:00
|
|
|
* Allow log_min_messages to be specified on a per-module basis
|
|
|
|
|
|
|
|
|
|
This would allow administrators to see more detailed information from
|
|
|
|
|
specific sections of the backend, e.g. checkpoints, autovacuum, etc.
|
2006-04-27 23:56:17 +08:00
|
|
|
Another idea is to allow separate configuration files for each module,
|
|
|
|
|
or allow arbitrary SET commands to be passed to them.
|
2004-11-02 22:49:27 +08:00
|
|
|
|
2006-09-03 07:47:39 +08:00
|
|
|
* Simplify ability to create partitioned tables
|
|
|
|
|
|
|
|
|
|
This would allow creation of partitioned tables without requiring
|
|
|
|
|
creation of rules for INSERT/UPDATE/DELETE, and constraints for
|
|
|
|
|
rapid partition selection. Options could include range and hash
|
|
|
|
|
partition selection.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-03-19 23:50:48 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php
|
2007-04-10 05:18:29 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php
|
2006-09-03 07:47:39 +08:00
|
|
|
|
|
|
|
|
* Allow auto-selection of partitioned tables for min/max() operations
|
2006-09-30 11:55:32 +08:00
|
|
|
* Allow more complex user/database default GUC settings
|
2006-04-11 07:15:46 +08:00
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently ALTER USER and ALTER DATABASE support per-user and
|
2006-09-30 11:55:32 +08:00
|
|
|
per-database defaults. Consider adding per-user-and-database
|
2007-08-28 11:00:36 +08:00
|
|
|
defaults so things like search_path can be defaulted for a
|
2006-09-30 11:55:32 +08:00
|
|
|
specific user connecting to a specific database.
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
|
2007-02-04 12:06:08 +08:00
|
|
|
* Allow custom variable classes that can restrict who can set the values
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
|
|
|
|
|
|
2007-05-18 06:44:11 +08:00
|
|
|
* Implement the SQL standard mechanism whereby REVOKE ROLE revokes only
|
|
|
|
|
the privilege granted by the invoking role, and not those granted
|
|
|
|
|
by other roles
|
|
|
|
|
|
2007-05-18 06:53:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php
|
|
|
|
|
|
2007-02-04 12:06:08 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Improve replication solutions
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Load balancing
|
2005-02-22 01:30:33 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
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.
|
2005-02-22 01:30:33 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Allow replication over unreliable or non-persistent links
|
2005-06-25 05:28:30 +08:00
|
|
|
|
|
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Configuration files
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2007-04-22 21:28:43 +08:00
|
|
|
o -Allow commenting of variables in postgresql.conf to restore them
|
2005-07-05 01:00:32 +08:00
|
|
|
to defaults
|
2006-02-13 11:55:02 +08:00
|
|
|
o Allow pg_hba.conf to specify host names along with IP addresses
|
|
|
|
|
|
|
|
|
|
Host name lookup could occur when the postmaster reads the
|
|
|
|
|
pg_hba.conf file, or when the backend starts. Another
|
|
|
|
|
solution would be to reverse lookup the connection IP and
|
|
|
|
|
check that hostname against the host names in pg_hba.conf.
|
|
|
|
|
We could also then check that the host name maps to the IP
|
|
|
|
|
address.
|
|
|
|
|
|
2005-08-24 22:05:37 +08:00
|
|
|
o %Allow postgresql.conf file values to be changed via an SQL
|
2005-07-31 21:54:52 +08:00
|
|
|
API, perhaps using SET GLOBAL
|
2005-07-25 23:27:06 +08:00
|
|
|
o 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-20 03:20:00 +08:00
|
|
|
o Issue a warning if a change-on-restart-only postgresql.conf value
|
2005-08-27 04:38:57 +08:00
|
|
|
is modified and the server config files are reloaded
|
|
|
|
|
o Mark change-on-restart-only values in postgresql.conf
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Tablespaces
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2006-06-10 02:41:57 +08:00
|
|
|
o Allow a database in tablespace t1 with tables created in
|
2005-07-05 01:00:32 +08:00
|
|
|
tablespace t2 to be used as a template for a new database created
|
|
|
|
|
with default tablespace t2
|
2004-07-11 08:18:28 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
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.
|
2005-04-18 20:51:41 +08:00
|
|
|
|
2006-06-10 02:41:57 +08:00
|
|
|
o Allow reporting of which objects are in which tablespaces
|
2005-04-18 20:51:41 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
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.
|
2004-08-16 12:38:46 +08:00
|
|
|
|
2007-01-25 12:38:59 +08:00
|
|
|
o -Add a GUC variable to control the tablespace for temporary objects
|
2005-07-05 01:00:32 +08:00
|
|
|
and sort files
|
|
|
|
|
o Allow WAL replay of CREATE TABLESPACE to work when the directory
|
|
|
|
|
structure on the recovery computer is different from the original
|
2004-12-03 03:32:57 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Allow per-tablespace quotas
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* Point-In-Time Recovery (PITR)
|
|
|
|
|
|
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 21:36:36 +08:00
|
|
|
o Allow a warm standby system to also allow read-only statements
|
2005-07-05 01:00:32 +08:00
|
|
|
[pitr]
|
|
|
|
|
|
|
|
|
|
This is useful for checking PITR recovery.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-04-03 06:50:19 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2006-09-26 19:18:29 +08:00
|
|
|
o %Create dump tool for write-ahead logs for use in determining
|
|
|
|
|
transaction id for point-in-time recovery
|
2005-07-05 01:00:32 +08:00
|
|
|
o Allow the PITR process to be debugged and data examined
|
2007-02-04 06:32:49 +08:00
|
|
|
o Allow recovery.conf to allow the same syntax as
|
|
|
|
|
postgresql.conf, including quoting
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
|
2006-07-26 00:23:42 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
|
|
|
|
|
Monitoring
|
|
|
|
|
==========
|
|
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
* -Allow server log information to be output as CSV format
|
2007-01-10 05:33:24 +08:00
|
|
|
* -Add ability to monitor the use of temporary sort files
|
2006-06-17 01:25:38 +08:00
|
|
|
|
2003-01-28 07:19:18 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Data Types
|
|
|
|
|
==========
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2007-01-07 06:24:16 +08:00
|
|
|
* -Make 64-bit version of the MONEY data type
|
|
|
|
|
* Add locale-aware MONEY type, and support multiple currencies
|
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-27 02:52:44 +08:00
|
|
|
|
2006-06-17 03:49:50 +08:00
|
|
|
http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
|
2007-03-22 00:43:31 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
|
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-27 02:52:44 +08:00
|
|
|
|
2005-12-03 01:39:44 +08:00
|
|
|
* Change NUMERIC to enforce the maximum precision
|
2007-03-30 05:43:34 +08:00
|
|
|
* Reduce storage space for small NUMERICs
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php
|
2007-03-30 05:44:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php
|
2007-03-30 05:43:34 +08:00
|
|
|
|
2004-07-21 03:52:03 +08:00
|
|
|
* Fix data types where equality comparison isn't intuitive, e.g. box
|
2005-08-27 21:52:07 +08:00
|
|
|
* Allow user-defined types to specify a type modifier at table creation
|
|
|
|
|
time
|
2007-01-07 06:19:46 +08:00
|
|
|
* -Allow user-defined types to accept 'typmod' parameters
|
2005-05-07 12:24:34 +08:00
|
|
|
|
2006-06-15 01:51:55 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php
|
2006-08-10 02:10:34 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2006-06-17 02:32:07 +08:00
|
|
|
* Add support for public SYNONYMs
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
|
|
|
|
|
|
2006-06-17 06:05:01 +08:00
|
|
|
* Fix CREATE CAST on DOMAINs
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php
|
2006-09-21 07:01:55 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php
|
2006-06-17 06:05:01 +08:00
|
|
|
|
2007-01-30 05:19:30 +08:00
|
|
|
* -Add Globally/Universally Unique Identifier (GUID/UUID)
|
2006-09-19 00:22:32 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php
|
2007-01-20 02:13:47 +08:00
|
|
|
http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php
|
2006-09-19 00:22:32 +08:00
|
|
|
|
2006-07-29 23:56:32 +08:00
|
|
|
* Add support for SQL-standard GENERATED/IDENTITY columns
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
|
2007-02-09 05:51:50 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
|
2007-05-15 10:36:43 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
|
2006-07-29 23:56:32 +08:00
|
|
|
|
2007-04-03 01:18:44 +08:00
|
|
|
* -Support a data type with specific enumerated values (ENUM)
|
2006-09-15 02:10:38 +08:00
|
|
|
* Improve XML support
|
|
|
|
|
|
|
|
|
|
http://developer.postgresql.org/index.php/XML_Support
|
|
|
|
|
|
2007-02-09 09:29:48 +08:00
|
|
|
* Consider placing all sequences in a single table, or create a system
|
|
|
|
|
view
|
2007-04-03 09:25:12 +08:00
|
|
|
* Allow all data types to cast to and from TEXT
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php
|
|
|
|
|
|
|
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* Dates and Times
|
|
|
|
|
|
2006-02-26 00:34:52 +08:00
|
|
|
o Allow infinite dates and intervals just like infinite timestamps
|
2007-08-28 11:00:36 +08:00
|
|
|
o Merge hardwired timezone names with the TZ database; allow either
|
2005-07-05 01:43:42 +08:00
|
|
|
kind everywhere a TZ name is currently taken
|
|
|
|
|
o Allow TIMESTAMP WITH TIME ZONE to store the original timezone
|
|
|
|
|
information, either zone name or offset from UTC [timezone]
|
|
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
If the TIMESTAMP value is stored with a time zone name, interval
|
2005-07-10 13:06:42 +08:00
|
|
|
computations should adjust based on the time zone rules.
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-08-27 04:38:57 +08:00
|
|
|
o Fix SELECT '0.01 years'::interval, '0.01 months'::interval
|
2007-08-28 11:00:36 +08:00
|
|
|
o Add a GUC variable to allow output of interval values in ISO8601
|
2005-10-27 10:33:31 +08:00
|
|
|
format
|
2007-04-03 06:46:10 +08:00
|
|
|
o Have timestamp subtraction not call justify_hours()?
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php
|
|
|
|
|
|
2005-10-27 10:33:31 +08:00
|
|
|
o Improve timestamptz subtraction to be DST-aware
|
|
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently subtracting one date from another that crosses a
|
2005-10-27 10:33:31 +08: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.
|
|
|
|
|
|
|
|
|
|
o Fix interval display to support values exceeding 2^31 hours
|
2007-04-03 06:46:10 +08:00
|
|
|
o Add overflow checking to timestamp and interval arithmetic
|
2007-01-11 12:27:29 +08:00
|
|
|
o Extend timezone code to allow 64-bit values so we can
|
|
|
|
|
represent years beyond 2038
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php
|
|
|
|
|
|
2007-02-15 05:00:17 +08:00
|
|
|
o Use LC_TIME for localized weekday/month names, rather than
|
|
|
|
|
LC_MESSAGES
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
|
|
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
o Add ISO INTERVAL handling
|
2006-06-17 00:59:30 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
|
2006-06-17 05:41:24 +08:00
|
|
|
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php
|
2006-06-17 00:59:30 +08:00
|
|
|
|
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 08:01:44 +08:00
|
|
|
o Support ISO INTERVAL syntax if units cannot be determined from
|
|
|
|
|
the string, and are supplied after the string
|
|
|
|
|
|
2006-04-25 08:06:23 +08:00
|
|
|
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 08:01:44 +08:00
|
|
|
|
|
|
|
|
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 08:06:23 +08: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'.
|
|
|
|
|
|
|
|
|
|
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 08:01:44 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
|
|
|
|
|
o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
|
|
|
|
|
INTERVAL MONTH), and this should return '12 months'
|
|
|
|
|
o Round or truncate values to the requested precision, e.g.
|
|
|
|
|
INTERVAL '11 months' AS YEAR should return one or zero
|
|
|
|
|
o Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Arrays
|
2005-05-17 08:24:22 +08:00
|
|
|
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
o Delay resolution of array expression's data type so assignment
|
|
|
|
|
coercion can be performed on empty array expressions
|
2006-08-17 14:48:38 +08:00
|
|
|
o Add support for arrays of domains
|
2007-05-13 19:22:04 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php
|
|
|
|
|
|
|
|
|
|
o -Add support for arrays of complex types
|
2007-04-12 05:02:31 +08:00
|
|
|
o Allow single-byte header storage for array elements
|
2004-02-13 07:27:52 +08:00
|
|
|
|
2002-01-23 05:55:06 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* Binary Data
|
|
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Improve vacuum of large objects, like /contrib/vacuumlo?
|
2001-09-07 04:37:14 +08:00
|
|
|
o Add security checking for large objects
|
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-27 02:52:44 +08:00
|
|
|
o Auto-delete large objects when referencing row is deleted
|
2004-08-01 13:15:58 +08:00
|
|
|
|
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-27 02:52:44 +08:00
|
|
|
/contrib/lo offers this functionality.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
o Allow read/write into TOAST values like large objects
|
|
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
This requires the TOAST column to be stored EXTERNAL.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-06-15 03:32:48 +08:00
|
|
|
o Add API for 64-bit large object access
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
|
|
|
|
|
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
Functions
|
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
* Allow INET subnet tests using non-constants to be indexed
|
2006-03-03 10:18:09 +08:00
|
|
|
* Allow to_date() and to_timestamp() accept localized month names
|
2007-04-03 05:25:34 +08:00
|
|
|
* Fix to_date()-related functions to consistently issue errors
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
|
|
|
|
|
|
2006-03-03 10:38:57 +08:00
|
|
|
* Add missing parameter handling in to_char()
|
|
|
|
|
|
2007-07-17 08:07:54 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php
|
2006-03-03 10:38:57 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Allow functions to have a schema search path specified at creation time
|
|
|
|
|
* Allow substring/replace() to get/set bit values
|
|
|
|
|
* Allow to_char() on interval values to accumulate the highest unit
|
|
|
|
|
requested
|
|
|
|
|
|
|
|
|
|
Some special format flag would be required to request such
|
2007-08-28 11:00:36 +08:00
|
|
|
accumulation. Such functionality could also be added to EXTRACT.
|
2005-07-05 01:00:32 +08:00
|
|
|
Prevent accumulation that crosses the month/day boundary because of
|
|
|
|
|
the uneven number of days in a month.
|
|
|
|
|
|
|
|
|
|
o to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65
|
2007-08-28 11:00:36 +08:00
|
|
|
o to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
|
2005-07-05 01:00:32 +08:00
|
|
|
o to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
|
|
|
|
|
o to_char(INTERVAL '3 years 5 months','MM') => 41
|
|
|
|
|
|
2007-02-20 01:58:32 +08:00
|
|
|
* -Add ISO day of week format 'ID' to to_char() where Monday = 1
|
2007-02-20 01:21:24 +08:00
|
|
|
* -Add a field 'isoyear' to extract(), based on the ISO week
|
2007-01-17 04:58:38 +08:00
|
|
|
* Implement inlining of set-returning functions defined in SQL
|
2006-11-23 13:01:47 +08:00
|
|
|
* Allow SQL-language functions to return results from RETURNING queries
|
2007-02-14 10:49:37 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
|
|
|
|
|
|
2007-02-18 09:32:55 +08:00
|
|
|
* Allow SQL-language functions to reference parameters by parameter name
|
|
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently SQL-language functions can only refer to dollar parameters,
|
|
|
|
|
e.g. $1
|
2007-02-18 09:32:55 +08:00
|
|
|
|
2007-02-17 10:01:02 +08:00
|
|
|
* Add SPI_gettypmod() to return the typemod for a TupleDesc
|
2007-01-27 11:25:49 +08:00
|
|
|
* Enforce typmod for function inputs, function results and parameters for
|
|
|
|
|
spi_prepare'd statements called from PLs
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php
|
2005-08-25 01:56:20 +08:00
|
|
|
|
2007-02-17 10:01:02 +08:00
|
|
|
* Allow holdable cursors in SPI
|
2007-02-01 12:50:58 +08:00
|
|
|
* Tighten function permission checks
|
|
|
|
|
|
2007-02-01 12:51:31 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php
|
|
|
|
|
|
2007-02-20 22:17:24 +08:00
|
|
|
* Fix IS OF so it matches the ISO specification, and add documentation
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
|
2007-02-01 12:50:58 +08:00
|
|
|
|
2007-02-21 05:22:35 +08:00
|
|
|
* Add missing operators for geometric data types
|
|
|
|
|
|
|
|
|
|
Some geometric types do not have the full suite of geometric operators,
|
|
|
|
|
e.g. box @> point
|
|
|
|
|
|
2007-09-26 16:47:43 +08:00
|
|
|
* Implement Boyer-Moore searching in strpos()
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php
|
2007-02-21 05:22:35 +08:00
|
|
|
|
2007-02-01 12:50:58 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Multi-Language Support
|
|
|
|
|
======================
|
2001-05-11 01:29:55 +08:00
|
|
|
|
2001-05-17 11:22:53 +08:00
|
|
|
* Add NCHAR (as distinguished from ordinary varchar),
|
2004-04-08 03:14:21 +08:00
|
|
|
* Allow locale to be set at database creation
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-05-07 23:45:23 +08:00
|
|
|
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.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-08-11 23:53:39 +08:00
|
|
|
* Allow encoding on a per-column basis optionally using the ICU library:
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-06-15 02:47:53 +08:00
|
|
|
Right now only one encoding is allowed per database. [locale]
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-06-09 00:07:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
|
2006-08-11 23:53:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php
|
2006-09-15 01:14:53 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-06-15 02:47:53 +08:00
|
|
|
* Add CREATE COLLATE? [locale]
|
2000-06-14 10:57:08 +08:00
|
|
|
* Support multiple simultaneous character sets, per SQL92
|
2005-07-05 01:00:32 +08:00
|
|
|
* Improve UTF8 combined character handling?
|
2004-08-01 13:15:58 +08:00
|
|
|
* Add octet_length_server() and octet_length_client()
|
|
|
|
|
* Make octet_length_client() the same as octet_length()?
|
2005-08-21 09:04:45 +08:00
|
|
|
* Fix problems with wrong runtime encoding conversion for NLS message files
|
2006-06-15 05:10:50 +08:00
|
|
|
* Add URL to more complete multi-byte regression tests
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
|
2003-08-17 12:50:57 +08:00
|
|
|
|
2006-06-15 05:40:00 +08:00
|
|
|
* Fix ILIKE and regular expressions to handle case insensitivity
|
|
|
|
|
properly in multibyte encodings
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
|
2006-06-15 07:03:12 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
|
2006-06-15 05:40:00 +08:00
|
|
|
|
2006-09-18 23:52:23 +08:00
|
|
|
* Set client encoding based on the client operating system encoding
|
|
|
|
|
|
|
|
|
|
Currently client_encoding is set in postgresql.conf, which
|
|
|
|
|
defaults to the server encoding.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-09-29 01:43:36 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php
|
2006-09-18 23:52:23 +08:00
|
|
|
|
2007-03-23 04:55:19 +08:00
|
|
|
* Fix cases where invalid byte encodings are accepted by the database,
|
|
|
|
|
but throw an error on SELECT
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php
|
|
|
|
|
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Views / Rules
|
|
|
|
|
=============
|
1999-06-07 10:42:07 +08:00
|
|
|
|
2006-02-26 09:21:57 +08:00
|
|
|
* Automatically create rules on views so they are updateable, per SQL99
|
2004-11-08 22:54:00 +08:00
|
|
|
|
|
|
|
|
We can only auto-create rules for simple views. For more complex
|
2006-02-26 09:21:57 +08:00
|
|
|
cases users will still have to write rules manually.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-06-17 02:50:24 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php
|
2007-03-28 10:17:45 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php
|
2004-11-08 22:54:00 +08:00
|
|
|
|
2002-06-29 03:28:30 +08:00
|
|
|
* Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
|
2001-01-27 13:40:51 +08:00
|
|
|
* 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-27 02:52:44 +08:00
|
|
|
* Allow VIEW/RULE recompilation when the underlying tables change
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2005-08-27 21:38:43 +08:00
|
|
|
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.
|
|
|
|
|
|
2007-09-15 02:50:48 +08:00
|
|
|
* Make it possible to use RETURNING together with conditional DO INSTEAD
|
|
|
|
|
rules, such as for partitioning setups
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
|
|
|
|
|
|
2002-04-18 04:35:23 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
SQL Commands
|
|
|
|
|
============
|
1999-06-07 10:42:07 +08:00
|
|
|
|
2002-08-27 07:02:21 +08:00
|
|
|
* Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
|
2002-12-10 02:09:44 +08:00
|
|
|
* Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
|
2005-08-24 22:05:37 +08:00
|
|
|
* %Allow SET CONSTRAINTS to be qualified by schema/table name
|
|
|
|
|
* %Add a separate TRUNCATE permission
|
2005-07-30 11:15:22 +08:00
|
|
|
|
|
|
|
|
Currently only the owner can TRUNCATE a table because triggers are not
|
|
|
|
|
called, and the table is locked in exclusive mode.
|
|
|
|
|
|
2003-08-17 13:23:13 +08:00
|
|
|
* Allow PREPARE of cursors
|
2004-08-13 03:45:24 +08:00
|
|
|
* Allow finer control over the caching of prepared query plans
|
|
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently queries prepared via the libpq API are planned on first
|
2004-08-13 03:45:24 +08: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.
|
|
|
|
|
|
2007-02-14 12:19:37 +08:00
|
|
|
* Improve logging of prepared statements recovered during startup
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
|
|
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Allow LISTEN/NOTIFY to store info in memory rather than tables?
|
|
|
|
|
|
|
|
|
|
Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
|
|
|
|
|
such information in memory would improve performance.
|
|
|
|
|
|
2003-10-21 10:48:09 +08:00
|
|
|
* Add optional textual message to NOTIFY
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
This would allow an informational message to be added to the notify
|
|
|
|
|
message, perhaps indicating the row modified or other custom
|
|
|
|
|
information.
|
|
|
|
|
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
* Add a GUC variable to warn about non-standard SQL usage in queries
|
2005-12-02 06:07:59 +08:00
|
|
|
* Add SQL-standard MERGE command, typically used to merge two tables
|
2005-12-02 06:12:35 +08:00
|
|
|
[merge]
|
2005-12-02 06:07:59 +08:00
|
|
|
|
|
|
|
|
This is similar to UPDATE, then for unmatched rows, INSERT.
|
|
|
|
|
Whether concurrent access allows modifications which could cause
|
|
|
|
|
row loss is implementation independent.
|
|
|
|
|
|
|
|
|
|
* Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
|
2005-12-02 06:12:35 +08:00
|
|
|
[merge]
|
2005-11-16 07:08:24 +08:00
|
|
|
|
|
|
|
|
To implement this cleanly requires that the table have a unique index
|
2005-11-17 02:45:09 +08: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.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-03-03 11:08:46 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00501.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00536.php
|
|
|
|
|
|
2005-11-16 07:08:24 +08:00
|
|
|
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
* Add NOVICE output level for helpful messages like automatic sequence/index
|
|
|
|
|
creation
|
2007-04-13 03:38:26 +08:00
|
|
|
* -Add RESET SESSION command to reset all session state
|
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 21:36:36 +08:00
|
|
|
* Add GUC to issue notice about statements that use unjoined tables
|
2007-08-28 11:00:36 +08:00
|
|
|
* Allow EXPLAIN to identify tables that were skipped because of
|
2005-08-23 01:35:03 +08:00
|
|
|
constraint_exclusion
|
2007-06-14 05:38:00 +08:00
|
|
|
* Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
|
Remove completed TODO items:
< * -Make postmater and postgres options distinct so the postmaster -o
< option is no longer needed
< * -Allow pooled connections to list all prepared statements
<
< This would allow an application inheriting a pooled connection to know
< the statements prepared in the current session.
<
< * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have
< been addressed
< o -Add "include file" functionality in postgresql.conf
< o -Allow per-database permissions to be set via GRANT
<
< Allow database connection checks based on GRANT rules in
< addition to the existing access checks in pg_hba.conf.
<
< o -Issue a warning if a change-on-restart-only postgresql.conf value
> o Issue a warning if a change-on-restart-only postgresql.conf value
< o -Automatically force archiving of partially-filled WAL files when
< pg_stop_backup() is called or the server is stopped
< o -Add reporting of the current WAL file and offset, perhaps as
< part of partial log file archiving
< * -Allow server logs to be remotely read and removed using SQL commands
< * -Allow protocol-level BIND parameter values to be logged
< * -Zero umasked bits in conversion from INET cast to CIDR
< * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr
< * -Allow INET + INT8 to increment the host part of the address or
< throw an error on overflow
< * -Add 'tid != tid ' operator for use in corruption recovery
< o -Allow customization of the known set of TZ names (generalize the
< present australian_timezones hack)
< o -Allow timezone names in SQL strings, '2006-05-24 21:11
< Americas/New_York'::timestamptz
< o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO
< SECOND
< o -Allow NULLs in arrays
< * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
< functionality
<
< Current CURRENT_TIMESTAMP returns the start time of the current
< transaction, and gettimeofday() returns the wallclock time. This will
< make time reporting more consistent and will allow reporting of
< the statement start time.
<
< * -Allow to_char() to print localized month names
< * -Add sleep() function, remove from regress.c
< * -Allow user-defined functions retuning a domain value to enforce domain
< constraints
< * -Allow TRUNCATE ... CASCADE/RESTRICT
<
< This is like DELETE CASCADE, but truncates.
<
< * -Add COMMENT ON for all cluster global objects (roles, databases
< and tablespaces)
< * -Make row-wise comparisons work per SQL spec
<
< Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
< the SQL standard requires it to be processed as a column-by-column
< comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
<
< * -Enable escape_string_warning and standard_conforming_strings
> * Enable standard_conforming_strings
< o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT
< o -Allow an alias to be provided for the target table in
< UPDATE/DELETE (Neil)
< o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating
< multiple columns
< o -Add ALTER TABLE tab INHERIT / NO INHERIT parent
< o -Have COPY return the number of rows loaded/unloaded?
< o -Allow COPY (SELECT ...) TO 'filename'
<
< o -Allow pooled connections to list all open WITH HOLD cursors
<
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
<
< o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
< o -Allow INSERT/UPDATE ... RETURNING new.col or old.col
< o -Allow PL/python to return composite types and result sets
<
< * -Have initdb set the input DateStyle (MDY or DMY) based on locale
< o -Improve psql's handling of multi-line statements
<
< Currently, while \e saves a single statement as one entry, interactive
< statements are saved one line at a time. Ideally all statements
< would be saved like \e does.
<
< o -Allow multi-line column values to align in the proper columns
<
< If the second output column value is 'a\nb', the 'b' should appear
< in the second display column, rather than the first column as it
< does now.
<
< o -Display IN, INOUT, and OUT parameters in \df
< o -Allow pg_dump to use multiple -t and -n switches, exclusion
< ability, and regular expression object matching
< o -Update pg_dump and psql to use the new COPY libpq API (Christopher)
< o -Add a function to support Parse/DescribeStatement capability
< * -Add fillfactor to control reserved free space during index creation
< * -Add system view to show free space map contents
< * -Allow installing to directories containing spaces
<
< This is possible if proper quoting is added to the makefiles for the
< install targets. Because PostgreSQL supports relocatable installs, it
< is already possible to install into a directory that doesn't contain
< spaces and then copy the install to a directory with spaces.
<
< * -%Clean up compiler warnings (especially with gcc version 4)
< * -Remove BeOS and QNX-specific code
< o -Port contrib/xml2
2006-09-20 03:20:00 +08:00
|
|
|
* Enable standard_conforming_strings
|
2007-04-29 15:17:12 +08:00
|
|
|
* Make standard_conforming_strings the default in 8.4?
|
2006-04-23 12:00:06 +08:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2005-09-24 05:55:01 +08:00
|
|
|
* Simplify dropping roles that have objects in several databases
|
2005-11-29 06:21:58 +08:00
|
|
|
* Allow COMMENT ON to accept an expression rather than just a string
|
2005-12-17 09:48:37 +08:00
|
|
|
* Allow the count returned by SELECT, etc to be to represent as an int64
|
|
|
|
|
to allow a higher range of values
|
2006-02-01 08:07:26 +08:00
|
|
|
* Add SQL99 WITH clause to SELECT
|
2006-06-09 09:02:22 +08:00
|
|
|
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
|
2006-05-05 17:35:58 +08:00
|
|
|
* Add DEFAULT .. AS OWNER so permission checks are done as the table
|
|
|
|
|
owner
|
|
|
|
|
|
|
|
|
|
This would be useful for SERIAL nextval() calls and CHECK constraints.
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2006-07-29 03:00:45 +08:00
|
|
|
* Allow DISTINCT to work in multiple-argument aggregate calls
|
2006-07-30 02:08:36 +08:00
|
|
|
* Add column to pg_stat_activity that shows the progress of long-running
|
|
|
|
|
commands like CREATE INDEX and VACUUM
|
2006-08-26 07:43:46 +08:00
|
|
|
* Implement SQL:2003 window functions
|
2007-02-14 03:57:09 +08:00
|
|
|
* Improve failure message when DROP DATABASE is used on a database that
|
|
|
|
|
has prepared transactions
|
2007-02-20 04:06:56 +08:00
|
|
|
* Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php
|
|
|
|
|
|
2007-02-21 06:29:28 +08:00
|
|
|
* Increase locking when DROPing objects so dependent objects cannot
|
|
|
|
|
get dropped while the DROP operation is happening
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* CREATE
|
|
|
|
|
|
|
|
|
|
o Allow CREATE TABLE AS to determine column lengths for complex
|
|
|
|
|
expressions like SELECT col1 || col2
|
|
|
|
|
o Use more reliable method for CREATE DATABASE to get a consistent
|
|
|
|
|
copy of db?
|
2007-01-11 12:48:03 +08:00
|
|
|
o Fix transaction restriction checks for CREATE DATABASE and
|
|
|
|
|
other commands
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2007-04-10 09:22:12 +08:00
|
|
|
o Have WITH CONSTRAINTS also create constraint indexes
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-04-10 09:22:12 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
|
2005-07-05 01:43:42 +08:00
|
|
|
|
|
|
|
|
* UPDATE
|
2006-09-03 04:31:50 +08:00
|
|
|
o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2006-07-28 06:05:49 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php
|
2007-04-03 09:16:24 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2007-06-02 02:40:42 +08:00
|
|
|
o Research self-referential UPDATEs that see inconsistent row versions
|
|
|
|
|
in read-committed mode
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
|
2007-06-02 02:41:55 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php
|
2007-06-02 02:40:42 +08:00
|
|
|
|
2007-07-18 08:16:21 +08:00
|
|
|
o Allow GLOBAL temporary tables to exist as empty by default in
|
|
|
|
|
all sessions
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php
|
|
|
|
|
|
|
|
|
|
|
2001-05-11 04:26:45 +08:00
|
|
|
* ALTER
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-08-24 22:05:37 +08:00
|
|
|
o %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-27 02:52:44 +08:00
|
|
|
o Add ALTER DOMAIN to modify the underlying data type
|
2006-02-13 03:13:19 +08:00
|
|
|
o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
|
2006-06-08 11:17:11 +08:00
|
|
|
|
2006-06-09 00:07:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
|
2006-06-08 11:17:11 +08:00
|
|
|
|
2005-08-24 22:05:37 +08:00
|
|
|
o %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-27 02:52:44 +08:00
|
|
|
o Add missing object types for ALTER ... SET SCHEMA
|
2004-08-01 13:15:58 +08:00
|
|
|
o Allow ALTER TABLESPACE to move to different directories
|
2005-06-09 11:00:43 +08:00
|
|
|
o Allow databases to be moved to different tablespaces
|
2004-08-01 13:15:58 +08:00
|
|
|
o Allow moving system tables to other tablespaces, where possible
|
|
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
Currently non-global system tables must be in the default database
|
2005-06-09 11:00:43 +08:00
|
|
|
tablespace. Global system tables can never be moved.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-03-07 01:10:31 +08:00
|
|
|
o Prevent parent tables from altering or dropping constraints
|
2006-04-25 10:58:34 +08:00
|
|
|
like CHECK that are inherited by child tables unless CASCADE
|
|
|
|
|
is used
|
|
|
|
|
o %Prevent child tables from altering or dropping constraints
|
|
|
|
|
like CHECK that were inherited from the parent table
|
2005-10-27 22:07:29 +08:00
|
|
|
o Have ALTER INDEX update the name of a constraint using that index
|
2005-10-27 22:16:05 +08:00
|
|
|
o Add ALTER TABLE RENAME CONSTRAINT, update index name also
|
2007-02-02 13:42:56 +08:00
|
|
|
o Allow column display reordering by recording a display,
|
|
|
|
|
storage, and permanent id for every column?
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php
|
|
|
|
|
|
2005-05-31 05:12:23 +08:00
|
|
|
|
2002-01-23 05:55:06 +08:00
|
|
|
|
2001-01-12 05:07:07 +08:00
|
|
|
* CLUSTER
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2007-04-08 10:17:02 +08:00
|
|
|
o -Make CLUSTER preserve recently-dead tuples per MVCC requirements
|
2002-01-23 05:55:06 +08:00
|
|
|
o Automatically maintain clustering on a table
|
2004-08-01 13:15:58 +08:00
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
This might require some background daemon to maintain clustering
|
|
|
|
|
during periods of low usage. It might also require tables to be only
|
2005-12-17 02:44:07 +08:00
|
|
|
partially filled for easier reorganization. Another idea would
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
be to create a merged heap/index data file so an index lookup would
|
2004-11-04 03:28:11 +08:00
|
|
|
automatically access the heap data too. A third idea would be to
|
2004-11-04 03:38:20 +08:00
|
|
|
store heap rows in hashed groups, perhaps using a user-supplied
|
|
|
|
|
hash function.
|
2006-08-10 00:42:19 +08:00
|
|
|
http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-08-24 22:05:37 +08:00
|
|
|
o %Add default clustering to system tables
|
2002-01-23 05:55:06 +08:00
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
To do this, determine the ideal cluster index for each system
|
|
|
|
|
table and set the cluster setting during initdb.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2007-03-23 04:38:42 +08:00
|
|
|
o %Add VERBOSE option to report tables as they are processed,
|
|
|
|
|
like VACUUM VERBOSE
|
2007-04-08 08:36:08 +08:00
|
|
|
o -Add more logical syntax CLUSTER table USING index;
|
2007-03-25 07:12:34 +08:00
|
|
|
support current syntax for backward compatibility
|
2007-03-23 04:38:42 +08:00
|
|
|
|
2004-11-11 12:36:55 +08:00
|
|
|
|
2001-05-11 04:26:45 +08:00
|
|
|
* COPY
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
o Allow COPY to report error lines and continue
|
2005-04-18 20:51:41 +08:00
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
This requires the use of a savepoint before each COPY line is
|
|
|
|
|
processed, with ROLLBACK on COPY failure.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-09-03 05:10:59 +08:00
|
|
|
o Allow COPY on a newly-created table to skip WAL logging
|
2004-11-30 11:53:00 +08:00
|
|
|
|
2005-09-03 05:10:59 +08:00
|
|
|
On crash recovery, the table involved in the COPY would
|
2005-09-17 00:46:09 +08:00
|
|
|
be removed or have its heap and index files truncated. One
|
2007-08-28 11:00:36 +08:00
|
|
|
issue is that no other backend should be able to add to
|
|
|
|
|
the table at the same time, which is something that is
|
2005-09-03 05:23:05 +08:00
|
|
|
currently allowed.
|
2004-11-11 12:36:55 +08:00
|
|
|
|
2005-09-23 00:01:59 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* GRANT/REVOKE
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Allow column-level privileges
|
2005-08-24 22:05:37 +08:00
|
|
|
o %Allow GRANT/REVOKE permissions to be applied to all schema objects
|
2005-08-01 22:05:03 +08:00
|
|
|
with one command
|
2005-07-05 01:00:32 +08:00
|
|
|
|
|
|
|
|
The proposed syntax is:
|
|
|
|
|
GRANT SELECT ON ALL TABLES IN public TO phpuser;
|
|
|
|
|
GRANT SELECT ON NEW TABLES IN public TO phpuser;
|
|
|
|
|
|
2006-06-10 02:41:57 +08:00
|
|
|
o Allow GRANT/REVOKE permissions to be inherited by objects based on
|
2005-07-05 01:00:32 +08:00
|
|
|
schema permissions
|
|
|
|
|
|
2006-06-10 02:41:57 +08:00
|
|
|
o Allow SERIAL sequences to inherit permissions from the base table?
|
2006-01-06 01:47:53 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2001-05-11 04:26:45 +08:00
|
|
|
* CURSOR
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2007-06-11 09:51:50 +08:00
|
|
|
o -Allow UPDATE/DELETE WHERE CURRENT OF cursor
|
2004-08-01 13:15:58 +08:00
|
|
|
o Prevent DROP TABLE from dropping a row referenced by its own open
|
2005-07-05 01:00:32 +08:00
|
|
|
cursor?
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2004-11-11 12:36:55 +08:00
|
|
|
|
2001-05-11 04:26:45 +08:00
|
|
|
* INSERT
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
o Allow INSERT/UPDATE of the system-generated oid value for a row
|
2006-08-02 21:29:54 +08:00
|
|
|
o In rules, allow VALUES() to contain a mixture of 'old' and 'new'
|
|
|
|
|
references
|
2002-01-23 05:55:06 +08:00
|
|
|
|
2004-11-11 12:36:55 +08:00
|
|
|
|
2001-05-11 04:26:45 +08:00
|
|
|
* SHOW/SET
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2001-07-16 13:00:29 +08:00
|
|
|
o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
|
2001-05-11 04:26:45 +08:00
|
|
|
ANALYZE, and CLUSTER
|
2005-07-05 01:00:32 +08:00
|
|
|
o Add SET PATH for schemas?
|
2004-08-01 13:15:58 +08:00
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
This is basically the same as SET search_path.
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
|
2004-11-11 12:36:55 +08:00
|
|
|
|
2006-05-23 04:39:23 +08:00
|
|
|
* Referential Integrity
|
|
|
|
|
|
|
|
|
|
o Add MATCH PARTIAL referential integrity
|
|
|
|
|
o Change foreign key constraint for array -> element to mean element
|
|
|
|
|
in array?
|
|
|
|
|
o Enforce referential integrity for system tables
|
2006-06-15 02:36:57 +08:00
|
|
|
o Fix problem when cascading referential triggers make changes on
|
|
|
|
|
cascaded tables, seeing the tables in an intermediate state
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
|
2006-05-23 04:39:23 +08:00
|
|
|
|
2006-08-29 07:21:46 +08:00
|
|
|
o Allow DEFERRABLE and end-of-statement UNIQUE constraints?
|
|
|
|
|
|
|
|
|
|
This would allow UPDATE tab SET col = col + 1 to work if col has
|
|
|
|
|
a unique index. Currently, uniqueness checks are done while the
|
|
|
|
|
command is being executed, rather than at the end of the statement
|
|
|
|
|
or transaction.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-08-29 07:22:57 +08:00
|
|
|
http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html
|
2006-09-18 22:56:19 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php
|
2006-08-29 07:21:46 +08:00
|
|
|
|
2006-05-23 04:39:23 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* Server-Side Languages
|
|
|
|
|
|
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-16 00:54:13 +08:00
|
|
|
o PL/pgSQL
|
|
|
|
|
o Fix RENAME to work on variables other than OLD/NEW
|
2007-01-31 12:23:47 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php
|
2007-02-01 08:32:45 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php
|
2007-02-03 05:34:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
|
2007-01-31 12:23:47 +08:00
|
|
|
|
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-16 00:54:13 +08:00
|
|
|
o Allow function parameters to be passed by name,
|
2006-06-16 12:04:52 +08:00
|
|
|
get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
|
2006-08-09 03:02:13 +08:00
|
|
|
o Add Oracle-style packages (Pavel)
|
2006-08-09 03:03:59 +08:00
|
|
|
|
2006-08-09 22:55:39 +08:00
|
|
|
A package would be a schema with session-local variables,
|
2006-08-09 10:48:10 +08:00
|
|
|
public/private functions, and initialization functions. It
|
2006-08-09 06:51:37 +08:00
|
|
|
is also possible to implement these capabilities
|
|
|
|
|
in all schemas and not use a separate "packages"
|
|
|
|
|
syntax at all.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-08-09 22:55:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
|
2006-08-09 03:03:59 +08:00
|
|
|
|
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-16 00:54:13 +08:00
|
|
|
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 single-step debugging of functions
|
2007-04-29 14:48:11 +08:00
|
|
|
o -Add support for MOVE cursors
|
|
|
|
|
o Add support for SCROLL cursors
|
2007-04-18 07:54:32 +08:00
|
|
|
o Add support for WITH HOLD cursors
|
2007-04-03 04:10:16 +08:00
|
|
|
o Allow RETURN to return row or record functions
|
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-16 00:54:13 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
|
2007-04-03 04:10:16 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php
|
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-16 00:54:13 +08:00
|
|
|
|
2006-06-17 01:44:43 +08:00
|
|
|
o Fix problems with RETURN NEXT on tables with
|
|
|
|
|
dropped/added columns after function creation
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
|
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-16 00:54:13 +08:00
|
|
|
|
2007-02-17 09:35:41 +08:00
|
|
|
o Allow row and record variables to be set to NULL constants,
|
|
|
|
|
and allow NULL tests on such variables
|
|
|
|
|
|
|
|
|
|
Because a row is not scalar, do not allow assignment
|
|
|
|
|
from NULL-valued scalars.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-02-21 09:08:58 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php
|
2007-02-17 09:35:41 +08:00
|
|
|
|
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-16 00:54:13 +08:00
|
|
|
o Other
|
2007-04-03 05:28:10 +08:00
|
|
|
o Add table function support to pltcl, plpythonu
|
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-16 00:54:13 +08:00
|
|
|
o Add support for polymorphic arguments and return types to
|
|
|
|
|
languages other than PL/PgSQL
|
|
|
|
|
o Add capability to create and call PROCEDURES
|
2007-08-28 11:00:36 +08:00
|
|
|
o Add support for OUT and INOUT parameters to languages other
|
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-16 00:54:13 +08:00
|
|
|
than PL/PgSQL
|
2007-04-03 05:28:10 +08:00
|
|
|
o Add PL/PythonU tracebacks
|
2006-06-17 02:11:03 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php
|
2002-08-14 10:51:13 +08:00
|
|
|
|
2007-04-03 23:51:36 +08:00
|
|
|
o -Allow PL/PythonU to return boolean rather than 1/0
|
2007-05-13 06:06:42 +08:00
|
|
|
o Allow data to be passed in native language formats, rather
|
|
|
|
|
than only text
|
2007-04-03 05:10:53 +08:00
|
|
|
|
2007-05-13 06:06:42 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
|
2007-04-03 05:10:53 +08:00
|
|
|
|
2002-10-04 10:28:42 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Clients
|
|
|
|
|
=======
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* Have pg_ctl look at PGHOST in case it is a socket directory?
|
|
|
|
|
* Allow pg_ctl to work properly with configuration files located outside
|
|
|
|
|
the PGDATA directory
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
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.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2007-01-07 06:18:24 +08:00
|
|
|
* 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-05 01:43:42 +08:00
|
|
|
|
|
|
|
|
* psql
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
o Have psql show current values for a sequence
|
|
|
|
|
o Move psql backslash database information into the backend, use
|
|
|
|
|
mnemonic commands? [psql]
|
|
|
|
|
|
|
|
|
|
This would allow non-psql clients to pull the same information out
|
|
|
|
|
of the database as psql.
|
|
|
|
|
|
2006-04-23 02:18:24 +08:00
|
|
|
o Fix psql's \d commands more consistent
|
2006-04-23 00:06:44 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
|
2006-04-23 02:17:57 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
|
2006-04-23 00:06:44 +08:00
|
|
|
|
2007-03-04 01:24:04 +08:00
|
|
|
o -Allow psql \pset boolean variables to set to fixed values, rather
|
2005-07-05 01:43:42 +08:00
|
|
|
than toggle
|
|
|
|
|
o Consistently display privilege information for all objects in psql
|
2005-10-26 02:50:56 +08:00
|
|
|
o Add auto-expanded mode so expanded output is used if the row
|
2007-08-28 11:00:36 +08:00
|
|
|
length is wider than the screen width.
|
2005-10-26 02:50:56 +08:00
|
|
|
|
|
|
|
|
Consider using auto-expanded mode for backslash commands like \df+.
|
|
|
|
|
|
2006-02-01 08:03:09 +08:00
|
|
|
o Prevent tab completion of SET TRANSACTION from querying the
|
|
|
|
|
database and therefore preventing the transaction isolation
|
|
|
|
|
level from being set.
|
|
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently SET <tab> causes a database lookup to check all
|
2006-02-01 08:03:09 +08:00
|
|
|
supported session variables. This query causes problems
|
|
|
|
|
because setting the transaction isolation level must be the
|
|
|
|
|
first statement of a transaction.
|
|
|
|
|
|
2007-01-07 05:58:22 +08:00
|
|
|
o Consider parsing the -c string into individual queries so each
|
|
|
|
|
is run in its own transaction
|
|
|
|
|
|
2007-01-11 12:49:01 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php
|
|
|
|
|
|
2007-02-06 01:17:13 +08:00
|
|
|
o Add a \set variable to control whether \s displays line numbers
|
2007-02-04 09:50:59 +08:00
|
|
|
|
2007-02-06 01:17:13 +08:00
|
|
|
Another option is to add \# which lists line numbers, and
|
|
|
|
|
allows command execution.
|
2007-02-04 09:50:59 +08:00
|
|
|
|
2007-02-06 01:17:13 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
|
2007-02-04 09:50:59 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2004-08-18 11:19:42 +08:00
|
|
|
* pg_dump
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-10-12 21:41:08 +08:00
|
|
|
o %Add dumping of comments on index columns and composite type columns
|
2005-08-24 22:05:37 +08:00
|
|
|
o %Add full object name to the tag field. eg. for operators we need
|
2004-08-18 11:19:42 +08: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-27 02:52:44 +08:00
|
|
|
o Add pg_dumpall custom format dumps?
|
|
|
|
|
o Remove unnecessary function pointer abstractions in pg_dump source
|
|
|
|
|
code
|
2005-10-12 07:55:10 +08:00
|
|
|
o Allow selection of individual object(s) of all types, not just
|
|
|
|
|
tables
|
2007-07-17 08:07:54 +08:00
|
|
|
o In a selective dump, allow dumping of an object and all its
|
2005-10-12 07:55:10 +08:00
|
|
|
dependencies
|
2005-10-12 10:57:42 +08:00
|
|
|
o Add options like pg_restore -l and -L to pg_dump
|
2005-10-12 21:41:08 +08:00
|
|
|
o Stop dumping CASCADE on DROP TYPE commands in clean mode
|
2005-10-12 21:39:21 +08:00
|
|
|
o Allow pg_dump --clean to drop roles that own objects or have
|
|
|
|
|
privileges
|
2007-01-25 10:48:06 +08:00
|
|
|
o -Add -f to pg_dumpall
|
2005-10-12 21:39:51 +08:00
|
|
|
|
2005-11-24 12:40:27 +08:00
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* ecpg
|
|
|
|
|
|
2003-06-15 18:34:10 +08:00
|
|
|
o Docs
|
2004-08-01 13:15:58 +08:00
|
|
|
|
Improve indentation of sublists:
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
> The proper solution to this will probably the use of a master/slave
> replication solution like Sloney and a connection pooling tool like
> pgpool.
114,116c114,116
< 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.
> 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.
166,167c166,167
< Currently large objects entries do not have owners. Permissions can
< only be set at the pg_largeobject table level.
> Currently large objects entries do not have owners. Permissions can
> only be set at the pg_largeobject table level.
173c173
< This requires the TOAST column to be stored EXTERNAL.
> This requires the TOAST column to be stored EXTERNAL.
359,360c359,360
< One complexity is whether moving a schema should move all existing
< schema objects or just define the location for future object creation.
> One complexity is whether moving a schema should move all existing
> schema objects or just define the location for future object creation.
364,365c364,365
< Currently non-global system tables must be in the default database
< schema. Global system tables can never be moved.
> Currently non-global system tables must be in the default database
> schema. Global system tables can never be moved.
371,375c371,375
< This might require some background daemon to maintain clustering
< during periods of low usage. It might also require tables to be only
< paritally filled for easier reorganization. Another idea would
< be to create a merged heap/index data file so an index lookup would
< automatically access the heap data too.
> This might require some background daemon to maintain clustering
> during periods of low usage. It might also require tables to be only
> paritally filled for easier reorganization. Another idea would
> be to create a merged heap/index data file so an index lookup would
> automatically access the heap data too.
379,380c379,380
< To do this, determine the ideal cluster index for each system
< table and set the cluster setting during initdb.
> To do this, determine the ideal cluster index for each system
> table and set the cluster setting during initdb.
385,386c385,386
< This requires the use of a savepoint before each COPY line is
< processed, with ROLLBACK on COPY failure.
> This requires the use of a savepoint before each COPY line is
> processed, with ROLLBACK on COPY failure.
395,398c395,398
< 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.
> 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.
405,406c405,406
< Because WITH HOLD cursors exist outside transactions, this allows
< them to be listed so they can be closed.
> Because WITH HOLD cursors exist outside transactions, this allows
> them to be listed so they can be closed.
413,415c413,415
< This is useful for returning the auto-generated key for an INSERT.
< One complication is how to handle rules that run as part of
< the insert.
> This is useful for returning the auto-generated key for an INSERT.
> One complication is how to handle rules that run as part of
> the insert.
422c422
< This is basically the same as SET search_path.
> This is basically the same as SET search_path.
426,427c426,427
< This requires a checking function to be called after the server
< configuration file is read.
> This requires a checking function to be called after the server
> configuration file is read.
432c432
< Currently only constants are supported.
> Currently only constants are supported.
438,439c438,439
< This requires the cached PL/PgSQL byte code to be invalidated when
< an object referenced in the function is changed.
> This requires the cached PL/PgSQL byte code to be invalidated when
> an object referenced in the function is changed.
512,513c512,513
< Document differences between ecpg and the SQL standard and
< information about the Informix-compatibility module.
> Document differences between ecpg and the SQL standard and
> information about the Informix-compatibility module.
2004-10-19 00:13:43 +08:00
|
|
|
Document differences between ecpg and the SQL standard and
|
|
|
|
|
information about the Informix-compatibility module.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Solve cardinality > 1 for input descriptors / variables?
|
2001-11-02 04:06:59 +08:00
|
|
|
o Add a semantic check level, e.g. check if a table really exists
|
2002-01-23 05:55:06 +08:00
|
|
|
o fix handling of DB attributes that are arrays
|
2004-05-07 10:40:43 +08:00
|
|
|
o Use backend PREPARE/EXECUTE facility for ecpg where possible
|
2003-08-09 02:55:35 +08:00
|
|
|
o Implement SQLDA
|
2003-06-15 18:34:10 +08:00
|
|
|
o Fix nested C comments
|
2005-08-24 22:05:37 +08:00
|
|
|
o %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified
|
2003-12-16 09:35:40 +08:00
|
|
|
o Make SET CONNECTION thread-aware, non-standard?
|
2004-03-07 22:35:47 +08:00
|
|
|
o Allow multidimensional arrays
|
2005-05-17 08:51:58 +08:00
|
|
|
o Add internationalized message strings
|
2006-08-09 06:39:09 +08:00
|
|
|
o Implement COPY FROM STDIN
|
1999-06-07 10:42:07 +08:00
|
|
|
|
2002-12-02 13:42:36 +08:00
|
|
|
|
2006-03-06 23:19:45 +08:00
|
|
|
* libpq
|
2005-11-17 00:33:44 +08:00
|
|
|
|
2006-07-04 21:22:41 +08:00
|
|
|
o Add PQescapeIdentifierConn()
|
2005-11-17 00:33:44 +08:00
|
|
|
o Prevent PQfnumber() from lowercasing unquoted the column name
|
|
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
PQfnumber() should never have been doing lowercasing, but
|
2005-11-17 00:33:44 +08:00
|
|
|
historically it has so we need a way to prevent it
|
|
|
|
|
|
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 21:36:36 +08:00
|
|
|
o Allow statement results to be automatically batched to the client
|
2005-11-17 00:33:44 +08:00
|
|
|
|
2007-02-18 09:34:35 +08:00
|
|
|
Currently all statement results are transferred to the libpq
|
2007-08-28 11:00:36 +08:00
|
|
|
client before libpq makes the results available to the
|
2005-11-17 00:33:44 +08:00
|
|
|
application. This feature would allow the application to make
|
2005-12-17 02:44:07 +08:00
|
|
|
use of the first result rows while the rest are transferred, or
|
2005-11-17 00:33:44 +08: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 21:36:36 +08:00
|
|
|
One complexity is that a statement like SELECT 1/col could error
|
2005-11-17 00:33:44 +08:00
|
|
|
out mid-way through the result set.
|
2007-01-07 05:58:22 +08:00
|
|
|
o Fix SSL retry to avoid useless repeated connection attempts and
|
2006-10-03 08:00:18 +08:00
|
|
|
ensuing misleading error messages
|
2007-01-07 05:58:22 +08:00
|
|
|
o Consider disallowing multiple queries in PQexec() as an
|
|
|
|
|
additional barrier to SQL injection attacks
|
2005-11-17 00:33:44 +08:00
|
|
|
|
2007-01-11 12:42:02 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php
|
|
|
|
|
|
2007-04-03 01:15:39 +08:00
|
|
|
o Add PQexecf() that allows complex parameter substitution
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php
|
2005-11-17 00:33:44 +08:00
|
|
|
|
2006-05-23 04:39:23 +08:00
|
|
|
Triggers
|
|
|
|
|
========
|
2006-09-30 11:55:32 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Add deferred trigger queue file
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2005-08-24 07:51:18 +08:00
|
|
|
* Allow triggers to be disabled in only the current session.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-08-24 07:51:18 +08:00
|
|
|
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 22:24:19 +08:00
|
|
|
TRIGGER requires a table lock so it is not ideal for this usage.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2003-05-24 09:27:41 +08:00
|
|
|
* With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
If the dump is known to be valid, allow foreign keys to be added
|
|
|
|
|
without revalidating the data.
|
|
|
|
|
|
2003-10-21 10:48:09 +08:00
|
|
|
* Allow statement-level triggers to access modified rows
|
2006-06-08 23:41:22 +08:00
|
|
|
* Support triggers on columns
|
|
|
|
|
|
2006-06-09 00:07:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php
|
2006-06-08 23:41:22 +08:00
|
|
|
|
2004-04-20 22:03:30 +08:00
|
|
|
* Allow AFTER triggers on system tables
|
2003-09-11 04:17:21 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
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 12:49:43 +08:00
|
|
|
* Tighten trigger permission checks
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
|
|
|
|
|
|
2007-03-25 10:21:19 +08:00
|
|
|
* Allow BEFORE INSERT triggers on views
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php
|
|
|
|
|
|
2007-02-01 12:49:43 +08:00
|
|
|
|
2002-08-14 10:51:13 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Dependency Checking
|
|
|
|
|
===================
|
2001-07-16 13:00:29 +08:00
|
|
|
|
2007-05-05 23:40:01 +08:00
|
|
|
* -Flush cached query plans when the dependent objects change or
|
2005-12-18 02:07:01 +08:00
|
|
|
when new ANALYZE statistics are available
|
2007-05-05 23:40:01 +08:00
|
|
|
* -Track dependencies in function bodies and recompile/invalidate
|
|
|
|
|
* -Invalidate prepared queries, like INSERT, when the table definition
|
2007-05-05 22:47:45 +08:00
|
|
|
is altered
|
|
|
|
|
|
2002-04-18 04:35:23 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
Indexes
|
|
|
|
|
=======
|
|
|
|
|
|
|
|
|
|
* Add UNIQUE capability to non-btree indexes
|
|
|
|
|
* Prevent index uniqueness checks when UPDATE does not modify the column
|
|
|
|
|
|
|
|
|
|
Uniqueness (index) checks are done when updating a column even if the
|
|
|
|
|
column is not modified by the UPDATE.
|
|
|
|
|
|
|
|
|
|
* Allow the creation of on-disk bitmap indexes which can be quickly
|
|
|
|
|
combined with other bitmap indexes
|
|
|
|
|
|
|
|
|
|
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-21 07:18:38 +08:00
|
|
|
|
2006-06-13 00:15:07 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
|
2007-01-21 07:18:38 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2007-04-07 11:08:20 +08:00
|
|
|
* -Allow use of indexes to search for NULLs
|
2005-07-05 01:00:32 +08:00
|
|
|
* Allow accurate statistics to be collected on indexes with more than
|
|
|
|
|
one column or expression indexes, perhaps using per-index statistics
|
2007-02-14 08:47:05 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php
|
2007-03-21 08:33:08 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php
|
2007-02-14 08:47:05 +08:00
|
|
|
|
2007-01-09 11:43:32 +08:00
|
|
|
* -Allow the creation of indexes with mixed ascending/descending
|
2006-04-09 11:27:06 +08:00
|
|
|
specifiers
|
2005-10-07 22:04:19 +08:00
|
|
|
* Consider compressing indexes by storing key values duplicated in
|
2005-10-07 10:43:59 +08:00
|
|
|
several rows as a single index entry
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2005-10-07 22:04:19 +08:00
|
|
|
This is difficult because it requires datatype-specific knowledge.
|
|
|
|
|
|
2007-01-31 11:17:49 +08:00
|
|
|
* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
|
|
|
|
|
|
|
|
|
|
This is difficult because you must upgrade to an exclusive table lock
|
|
|
|
|
to replace the existing index file. CREATE INDEX CONCURRENTLY does not
|
|
|
|
|
have this complication. This would allow index compaction without
|
|
|
|
|
downtime.
|
|
|
|
|
|
2007-07-17 08:07:54 +08:00
|
|
|
* Allow multiple indexes to be created concurrently, ideally via a
|
|
|
|
|
single heap scan, and have a restore of a pg_dump somehow use it
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
|
|
|
|
|
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2007-01-07 04:00:10 +08:00
|
|
|
* Inheritance
|
|
|
|
|
|
|
|
|
|
o Allow inherited tables to inherit indexes, UNIQUE constraints,
|
|
|
|
|
and primary/foreign keys
|
|
|
|
|
o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
|
|
|
|
|
on inherited table, e.g. INSERT INTO inherit_table
|
|
|
|
|
(unique_index_col) VALUES (dup) should fail
|
|
|
|
|
|
|
|
|
|
The main difficulty with this item is the problem of
|
|
|
|
|
creating an index that can span multiple tables.
|
|
|
|
|
|
|
|
|
|
o Allow SELECT ... FOR UPDATE on inherited tables
|
|
|
|
|
|
|
|
|
|
|
2005-07-05 01:43:42 +08:00
|
|
|
* GIST
|
|
|
|
|
|
|
|
|
|
o Add more GIST index support for geometric data types
|
|
|
|
|
o Allow GIST indexes to create certain complex index types, like
|
|
|
|
|
digital trees (see Aoki)
|
2005-07-05 01:00:32 +08:00
|
|
|
|
2007-01-07 04:00:10 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Hash
|
2007-09-08 03:07:58 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o 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-27 02:52:44 +08:00
|
|
|
Currently only one hash bucket can be stored on a page. Ideally
|
2005-07-05 01:00:32 +08:00
|
|
|
several hash buckets could be stored on a single page and greater
|
|
|
|
|
granularity used for the hash algorithm.
|
|
|
|
|
|
2007-01-17 04:58:38 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php
|
|
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
o Consider sorting hash buckets so entries can be found using a
|
|
|
|
|
binary search, rather than a linear scan
|
|
|
|
|
o 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-27 02:52:44 +08:00
|
|
|
o Add WAL logging for crash recovery
|
|
|
|
|
o Allow multi-column hash indexes
|
2007-03-22 05:25:46 +08:00
|
|
|
o During index creation, pre-sort the tuples to improve build speed
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php
|
|
|
|
|
|
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-27 02:52:44 +08:00
|
|
|
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Fsync
|
|
|
|
|
=====
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Improve commit_delay handling to reduce fsync()
|
2001-03-21 04:31:07 +08:00
|
|
|
* 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-27 02:52:44 +08:00
|
|
|
|
|
|
|
|
Ideally this requires a separate test program that can be run
|
2005-12-08 01:29:14 +08: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-27 02:52:44 +08:00
|
|
|
|
2005-08-24 22:05:37 +08:00
|
|
|
* %Add an option to sync() before fsync()'ing checkpoint files
|
2005-06-24 10:07:19 +08:00
|
|
|
* Add program to test if fsync has a delay compared to non-fsync
|
2007-06-29 05:55:00 +08:00
|
|
|
* -Reduce checkpoint performance degredation by forcing data to disk
|
2007-02-03 06:55:08 +08:00
|
|
|
more evenly
|
|
|
|
|
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
Cache Usage
|
|
|
|
|
===========
|
2005-04-18 22:42:35 +08:00
|
|
|
|
2007-06-02 19:28:01 +08:00
|
|
|
* Allow free-behind capability for large sequential scans to avoid
|
|
|
|
|
kernel cache spoiling
|
|
|
|
|
|
|
|
|
|
Posix_fadvise() can control both sequential/random file caching and
|
|
|
|
|
free-behind behavior, but it is unclear how the setting affects other
|
|
|
|
|
backends that also have the file open, and the feature is not supported
|
|
|
|
|
on all operating systems.
|
|
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Speed up COUNT(*)
|
|
|
|
|
|
|
|
|
|
We could use a fixed row count and a +/- count to follow MVCC
|
|
|
|
|
visibility rules, or a single cached value could be used and
|
2005-01-23 04:05:23 +08:00
|
|
|
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 04:58:38 +08:00
|
|
|
* Provide a way to calculate an "estimated COUNT(*)"
|
|
|
|
|
|
|
|
|
|
Perhaps by using the optimizer's cardinality estimates or random
|
|
|
|
|
sampling.
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
|
|
|
|
|
|
2005-01-23 04:05:23 +08:00
|
|
|
* Allow data to be pulled directly from indexes
|
|
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
Currently indexes do not have enough tuple visibility information
|
|
|
|
|
to allow data to be pulled from the index without also accessing
|
|
|
|
|
the heap. One way to allow this is to set a bit on index tuples
|
|
|
|
|
to indicate if a tuple is currently visible to all transactions
|
|
|
|
|
when the first valid heap lookup happens. This bit would have to
|
|
|
|
|
be cleared when a heap tuple is expired.
|
2005-12-02 12:28:19 +08:00
|
|
|
|
|
|
|
|
Another idea is to maintain a bitmap of heap pages where all rows
|
2007-08-28 11:00:36 +08:00
|
|
|
are visible to all backends, and allow index lookups to reference
|
2005-12-02 12:28:19 +08:00
|
|
|
that bitmap to avoid heap lookups, perhaps the same bitmap we might
|
|
|
|
|
add someday to determine which heap pages need vacuuming. Frequently
|
|
|
|
|
accessed bitmaps would have to be stored in shared memory. One 8k
|
|
|
|
|
page of bitmaps could track 512MB of heap pages.
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
A third idea would be for a heap scan to check if all rows are visible
|
|
|
|
|
and if so set a per-table flag which can be checked by index scans.
|
|
|
|
|
Any change to the table would have to clear the flag. To detect
|
|
|
|
|
changes during the heap scan a counter could be set at the start and
|
|
|
|
|
checked at the end --- if it is the same, the table has not been
|
|
|
|
|
modified --- any table change would increment the counter.
|
|
|
|
|
|
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 21:36:36 +08:00
|
|
|
* Consider automatic caching of statements at various levels:
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2004-09-27 22:17:51 +08:00
|
|
|
o Parsed query tree
|
|
|
|
|
o Query execute plan
|
|
|
|
|
o Query results
|
|
|
|
|
|
2007-06-09 02:45:22 +08:00
|
|
|
* -Allow sequential scans to take advantage of other concurrent
|
2005-12-17 02:44:07 +08:00
|
|
|
sequential scans, also called "Synchronised Scanning"
|
2006-06-15 06:31:53 +08:00
|
|
|
* Consider increasing internal areas when shared buffers is increased
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
|
|
|
|
|
|
2007-02-21 07:39:03 +08:00
|
|
|
* Consider decreasing the amount of memory used by PrivateRefCount
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
|
|
|
|
|
|
|
|
|
|
|
2005-07-04 20:32:38 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Vacuum
|
|
|
|
|
======
|
2001-03-01 02:07:15 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Improve speed with indexes
|
|
|
|
|
|
2007-04-03 06:49:03 +08:00
|
|
|
For large table adjustments during VACUUM FULL, it is faster to cluster
|
|
|
|
|
or reindex rather than update the index. Also, index updates can bloat
|
|
|
|
|
the index.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-04-03 06:49:03 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
|
2007-05-31 03:07:20 +08:00
|
|
|
http://archives.postgresql.org/pgsql-performance/2007-05/msg00296.php
|
2004-08-01 13:15:58 +08:00
|
|
|
|
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-27 02:52:44 +08:00
|
|
|
* Reduce lock time during VACUUM FULL by moving tuples with read lock,
|
|
|
|
|
then write lock and truncate table
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
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-18 03:20:27 +08:00
|
|
|
* Auto-fill the free space map by scanning the buffer cache or by
|
|
|
|
|
checking pages written by the background writer
|
2006-06-17 02:37:31 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php
|
2006-06-17 02:38:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php
|
2006-06-17 02:37:31 +08:00
|
|
|
|
2005-06-17 10:20:43 +08:00
|
|
|
* Create a bitmap of pages that need vacuuming
|
|
|
|
|
|
|
|
|
|
Instead of sequentially scanning the entire table, have the background
|
|
|
|
|
writer or some other process record pages that have expired rows, then
|
|
|
|
|
VACUUM can look at just those pages rather than the entire table. In
|
|
|
|
|
the event of a system crash, the bitmap would probably be invalidated.
|
2005-09-02 08:49:57 +08: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.
|
2005-06-17 10:20:43 +08:00
|
|
|
|
2007-01-21 07:08:20 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php
|
|
|
|
|
|
2006-03-03 11:13:04 +08:00
|
|
|
* 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 13:02:03 +08:00
|
|
|
* Allow FSM page return free space based on table clustering, to assist
|
|
|
|
|
in maintaining clustering?
|
2007-09-21 02:54:19 +08:00
|
|
|
* -Consider shrinking expired tuples to just their headers
|
|
|
|
|
* -Allow heap reuse of UPDATEd rows if no indexed columns are changed,
|
|
|
|
|
and old and new versions are on the same heap page
|
2007-03-27 07:48:43 +08:00
|
|
|
* Improve dead row detection during multi-statement transactions usage
|
2007-03-27 07:47:53 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
|
|
|
|
|
|
2007-09-06 05:58:47 +08:00
|
|
|
* -Reduce XID consumption of read-only queries
|
2004-11-29 10:29:28 +08:00
|
|
|
* Auto-vacuum
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2006-07-30 09:48:40 +08:00
|
|
|
o 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-27 02:52:44 +08:00
|
|
|
o %Issue log message to suggest VACUUM FULL if a table is nearly
|
|
|
|
|
empty?
|
2005-12-04 12:02:55 +08:00
|
|
|
o Consider logging activity either to the logs or a system view
|
2007-01-17 11:43:49 +08:00
|
|
|
o -Turn on by default
|
2007-05-05 22:44:15 +08:00
|
|
|
o -Allow multiple vacuums so large tables do not starve small
|
2007-01-20 05:36:07 +08:00
|
|
|
tables
|
|
|
|
|
o Improve control of auto-vacuum
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
|
2006-09-03 06:59:00 +08:00
|
|
|
|
2007-09-15 03:02:46 +08:00
|
|
|
o Prevent long-lived temporary tables from causing frozen-xid
|
|
|
|
|
advancement starvation
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php
|
|
|
|
|
|
2005-04-18 22:42:35 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Locking
|
|
|
|
|
=======
|
2002-01-23 04:50:35 +08:00
|
|
|
|
2004-12-03 10:24:01 +08:00
|
|
|
* Fix priority ordering of read and write light-weight locks (Neil)
|
2002-01-23 04:50:35 +08:00
|
|
|
|
2007-01-17 04:58:38 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php
|
|
|
|
|
|
2007-02-01 12:35:52 +08:00
|
|
|
* Fix problem when multiple subtransactions of the same outer transaction
|
|
|
|
|
hold different types of locks, and one subtransaction aborts
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
|
2007-02-09 11:39:39 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2007-02-20 04:41:40 +08:00
|
|
|
* Allow UPDATEs on only non-referential integrity columns not to conflict
|
|
|
|
|
with referential integrity locks
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php
|
2007-02-09 11:39:59 +08:00
|
|
|
|
2007-04-03 12:12:00 +08:00
|
|
|
* Add idle_in_transaction_timeout GUC so locks are not held for long
|
2007-04-03 10:17:11 +08:00
|
|
|
periods of time
|
2007-04-03 09:21:06 +08:00
|
|
|
|
2007-02-20 04:42:33 +08:00
|
|
|
|
|
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
Startup Time Improvements
|
|
|
|
|
=========================
|
1999-07-07 04:41:22 +08:00
|
|
|
|
2006-04-10 04:24:30 +08:00
|
|
|
* Experiment with multi-threaded backend for backend creation [thread]
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
This would prevent the overhead associated with process creation. Most
|
|
|
|
|
operating systems have trivial process creation time compared to
|
2005-12-17 02:44:07 +08:00
|
|
|
database startup overhead, but a few operating systems (Win32,
|
2005-04-24 05:39:27 +08: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 21:36:36 +08:00
|
|
|
a single session using multiple threads to execute a statement faster.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-04-10 04:24:30 +08:00
|
|
|
* Experiment with multi-threaded backend better resource utilization
|
|
|
|
|
|
|
|
|
|
This would allow a single query to make use of multiple CPU's or
|
2006-04-13 18:50:13 +08: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.
|
2006-04-10 04:24:30 +08:00
|
|
|
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
* Add connection pooling
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
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.
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2002-01-23 04:50:35 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Write-Ahead Log
|
|
|
|
|
===============
|
2002-01-23 04:50:35 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
* Eliminate need to write full pages to WAL before page modification [wal]
|
|
|
|
|
|
2005-07-04 12:06:43 +08:00
|
|
|
Currently, to protect against partial disk page writes, we write
|
2004-08-01 13:15:58 +08:00
|
|
|
full page images to WAL before they are modified so we can correct any
|
2004-08-24 05:56:50 +08:00
|
|
|
partial page writes during recovery. These pages can also be
|
|
|
|
|
eliminated from point-in-time archive files.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2005-07-07 23:18:26 +08:00
|
|
|
o When off, write CRC to WAL and check file system blocks
|
|
|
|
|
on recovery
|
2005-07-30 00:05:28 +08:00
|
|
|
|
|
|
|
|
If CRC check fails during recovery, remember the page in case
|
|
|
|
|
a later CRC for that page properly matches.
|
|
|
|
|
|
2005-07-07 23:18:26 +08:00
|
|
|
o Write full pages during file system write and not when
|
|
|
|
|
the page is modified in the buffer cache
|
|
|
|
|
|
|
|
|
|
This allows most full page writes to happen in the background
|
2005-07-08 00:02:06 +08: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 23:18:26 +08:00
|
|
|
|
2005-09-20 10:21:29 +08:00
|
|
|
* Allow WAL traffic to be streamed to another server for stand-by
|
2005-09-20 08:11:00 +08:00
|
|
|
replication
|
2004-08-01 13:15:58 +08:00
|
|
|
* Reduce WAL traffic so only modified values are written rather than
|
2007-04-05 10:08:53 +08:00
|
|
|
entire rows
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
|
|
|
|
|
|
2007-01-07 03:41:23 +08:00
|
|
|
* -Allow the pg_xlog directory location to be specified during initdb
|
2004-08-01 13:15:58 +08:00
|
|
|
with a symlink back to the /data location
|
2006-06-03 10:34:35 +08:00
|
|
|
* Allow WAL information to recover corrupted pg_controldata
|
2006-06-03 12:00:01 +08:00
|
|
|
|
2006-06-09 00:07:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
|
2006-06-03 12:00:01 +08:00
|
|
|
|
2003-05-24 23:33:46 +08:00
|
|
|
* Find a way to reduce rotational delay when repeatedly writing
|
|
|
|
|
last WAL page
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
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.
|
2002-02-04 03:24:30 +08:00
|
|
|
|
2007-08-02 07:13:31 +08:00
|
|
|
* -Allow buffered WAL writes and fsync
|
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 10:08:08 +08:00
|
|
|
* Allow WAL logging to be turned off for a table, but the table
|
|
|
|
|
might be dropped or truncated during crash recovery [walcontrol]
|
2006-01-06 00:23:48 +08:00
|
|
|
|
|
|
|
|
Allow tables to bypass WAL writes and just fsync() dirty pages on
|
2007-08-28 11:00:36 +08:00
|
|
|
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
|
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 10:08:08 +08:00
|
|
|
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]
|
|
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
To do this, only a single writer can modify the table, and writes
|
Split up wal-logging items:
< * Allow control over which tables are WAL-logged [walcontrol]
> * Allow WAL logging to be turned off for a table, but the table
> might be dropped or truncated during crash recovery [walcontrol]
< commit. To do this, only a single writer can modify the table, and
< writes must happen only on new pages. Readers can continue accessing
< the table. This would affect COPY, and perhaps INSERT/UPDATE too.
< Another option is to avoid transaction logging entirely and truncate
< or drop the table on crash recovery. These should be implemented
< using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
< STABLE | DEFAULT ]. Tables using non-default logging should not use
< referential integrity with default-logging tables, and tables using
< stable logging probably can not have indexes. One complexity is
< the handling of indexes on TOAST tables.
> commit. This should be implemented using ALTER TABLE, e.g. ALTER
> TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using
> non-default logging should not use referential integrity with
> default-logging tables. A table without dirty buffers during a
> crash could perhaps avoid the drop/truncate.
>
> * Allow WAL logging to be turned off for a table, but the table would
> avoid being truncated/dropped [walcontrol]
>
> To do this, only a single writer can modify the table, and writes
> must happen only on new pages so the new pages can be removed during
> crash recovery. Readers can continue accessing the table. Such
> tables probably cannot have indexes. One complexity is the handling
> of indexes on TOAST tables.
2006-02-07 10:08:08 +08:00
|
|
|
must happen only on new pages so the new pages can be removed during
|
2007-08-28 11:00:36 +08:00
|
|
|
crash recovery. Readers can continue accessing the table. Such
|
|
|
|
|
tables probably cannot have indexes. One complexity is the handling
|
Split up wal-logging items:
< * Allow control over which tables are WAL-logged [walcontrol]
> * Allow WAL logging to be turned off for a table, but the table
> might be dropped or truncated during crash recovery [walcontrol]
< commit. To do this, only a single writer can modify the table, and
< writes must happen only on new pages. Readers can continue accessing
< the table. This would affect COPY, and perhaps INSERT/UPDATE too.
< Another option is to avoid transaction logging entirely and truncate
< or drop the table on crash recovery. These should be implemented
< using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
< STABLE | DEFAULT ]. Tables using non-default logging should not use
< referential integrity with default-logging tables, and tables using
< stable logging probably can not have indexes. One complexity is
< the handling of indexes on TOAST tables.
> commit. This should be implemented using ALTER TABLE, e.g. ALTER
> TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using
> non-default logging should not use referential integrity with
> default-logging tables. A table without dirty buffers during a
> crash could perhaps avoid the drop/truncate.
>
> * Allow WAL logging to be turned off for a table, but the table would
> avoid being truncated/dropped [walcontrol]
>
> To do this, only a single writer can modify the table, and writes
> must happen only on new pages so the new pages can be removed during
> crash recovery. Readers can continue accessing the table. Such
> tables probably cannot have indexes. One complexity is the handling
> of indexes on TOAST tables.
2006-02-07 10:08:08 +08:00
|
|
|
of indexes on TOAST tables.
|
2006-01-06 00:23:48 +08:00
|
|
|
|
2005-04-18 22:42:35 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Optimizer / Executor
|
|
|
|
|
====================
|
2002-01-23 04:50:35 +08:00
|
|
|
|
2005-12-30 00:45:11 +08:00
|
|
|
* Improve selectivity functions for geometric operators
|
2007-05-05 11:14:40 +08:00
|
|
|
* -Allow ORDER BY ... LIMIT # to select high/low value without sort or
|
2005-04-25 21:03:37 +08:00
|
|
|
index using a sequential scan for highest/lowest values
|
2004-08-01 13:15:58 +08:00
|
|
|
* Precompile SQL functions to avoid overhead
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
* Create utility to compute accurate random_page_cost value
|
2002-04-24 04:26:29 +08:00
|
|
|
* Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
|
2006-12-13 06:31:19 +08:00
|
|
|
* Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and
|
|
|
|
|
actual row counts differ by a specified percentage
|
2004-09-02 09:18:46 +08:00
|
|
|
* Consider using hash buckets to do DISTINCT, rather than sorting
|
|
|
|
|
|
2005-09-21 04:51:30 +08:00
|
|
|
This would be beneficial when there are few distinct values. This is
|
|
|
|
|
already used by GROUP BY.
|
2002-08-14 10:51:13 +08:00
|
|
|
|
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 21:36:36 +08:00
|
|
|
* Log statements where the optimizer row estimates were dramatically
|
2005-07-05 01:00:32 +08:00
|
|
|
different from the number of rows actually found?
|
2006-08-01 07:04:13 +08:00
|
|
|
* Consider compressed annealing to search for query plans
|
|
|
|
|
|
|
|
|
|
This might replace GEQO, http://sixdemonbag.org/Djinni.
|
2002-10-04 10:28:42 +08:00
|
|
|
|
2007-08-28 11:00:36 +08:00
|
|
|
* Improve merge join performance by allowing mark/restore of
|
2007-01-10 06:43:31 +08:00
|
|
|
tuple sources
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php
|
|
|
|
|
|
|
|
|
|
|
2005-04-18 22:42:35 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
Miscellaneous Performance
|
|
|
|
|
=========================
|
2002-01-23 04:50:35 +08:00
|
|
|
|
|
|
|
|
* Do async I/O for faster random read-ahead of data
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
Async I/O allows multiple I/O requests to be sent to the disk with
|
|
|
|
|
results coming back asynchronously.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-10-22 01:31:18 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
|
2005-07-05 01:00:32 +08:00
|
|
|
* Use mmap() rather than SYSV shared memory or to write WAL files?
|
2004-08-01 13:15:58 +08:00
|
|
|
|
|
|
|
|
This would remove the requirement for SYSV SHM but would introduce
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
portability issues. Anonymous mmap (or mmap to /dev/zero) is required
|
|
|
|
|
to prevent I/O overhead.
|
2004-11-09 11:57:42 +08:00
|
|
|
|
|
|
|
|
* Consider mmap()'ing files into a backend?
|
|
|
|
|
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
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,
|
2004-11-09 11:57:42 +08:00
|
|
|
leading to thousands of mappings. Another problem is that there is no
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
way to _prevent_ I/O to disk from the dirty shared buffers so changes
|
2004-11-09 11:57:42 +08:00
|
|
|
could hit disk before WAL is written.
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2003-02-18 10:49:30 +08:00
|
|
|
* 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 11:37:45 +08:00
|
|
|
* -Merge xmin/xmax/cmin/cmax back into three header fields
|
2006-09-11 06:20:01 +08:00
|
|
|
* Consider ways of storing rows more compactly on disk
|
|
|
|
|
|
2007-04-07 10:48:16 +08:00
|
|
|
o -Support a smaller header for short variable-length fields
|
2006-09-11 06:20:01 +08:00
|
|
|
o Reduce the row header size?
|
2007-08-28 11:00:36 +08:00
|
|
|
o Consider reducing on-disk varlena length from four bytes to
|
2007-04-14 07:23:22 +08:00
|
|
|
two because a heap row cannot be more than 64k in length
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2007-01-27 10:28:16 +08:00
|
|
|
* Consider increasing NUM_CLOG_BUFFERS
|
2007-01-27 10:29:32 +08:00
|
|
|
* Consider having the background writer update the transaction status
|
|
|
|
|
hint bits before writing out the page
|
2007-02-20 05:08:48 +08:00
|
|
|
* Allow user configuration of TOAST thresholds
|
2007-02-20 05:07:25 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php
|
|
|
|
|
|
2007-03-27 23:36:40 +08:00
|
|
|
* Allow configuration of backend priorities via the operating system
|
|
|
|
|
|
|
|
|
|
Though backend priorities make priority inversion during lock
|
|
|
|
|
waits possible, research shows that this is not a huge problem.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2007-03-27 23:36:40 +08:00
|
|
|
http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php
|
|
|
|
|
|
2007-04-03 04:43:40 +08:00
|
|
|
* Consider reducing memory used for shared buffer reference count
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
|
|
|
|
|
|
2007-01-27 10:28:16 +08:00
|
|
|
|
2005-09-17 20:12:58 +08:00
|
|
|
|
2002-04-26 04:20:50 +08:00
|
|
|
Source Code
|
2002-02-04 03:24:30 +08:00
|
|
|
===========
|
|
|
|
|
|
1999-11-10 09:22:37 +08:00
|
|
|
* Add use of 'const' for variables in source tree
|
2001-11-23 10:22:04 +08:00
|
|
|
* Move some things from /contrib into main tree
|
2005-08-24 22:05:37 +08:00
|
|
|
* %Remove warnings created by -Wcast-align
|
2001-03-29 08:12:57 +08:00
|
|
|
* Move platform-specific ps status display info from ps_status.c to ports
|
2002-01-23 05:55:06 +08:00
|
|
|
* Add optional CRC checksum to heap and index pages
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
* Improve documentation to build only interfaces (Marc)
|
2002-02-22 08:10:11 +08:00
|
|
|
* 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-27 02:52:44 +08:00
|
|
|
* %Remove memory/file descriptor freeing before ereport(ERROR)
|
2002-11-02 13:42:01 +08:00
|
|
|
* 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-27 02:52:44 +08:00
|
|
|
* %Promote debug_query_string into a server-side function current_query()
|
2004-11-29 11:17:30 +08:00
|
|
|
* Allow cross-compiling by generating the zic database on the target system
|
2006-02-26 09:21:57 +08:00
|
|
|
* Improve NLS maintenance of libpgport messages linked onto applications
|
2004-12-02 01:39:18 +08:00
|
|
|
* Allow ecpg to work with MSVC and BCC
|
2005-02-15 10:27:36 +08:00
|
|
|
* Add xpath_array() to /contrib/xml2 to return results as an array
|
2007-02-14 12:24:42 +08:00
|
|
|
* Clean up casting in /contrib/isn
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php
|
|
|
|
|
|
2005-01-04 13:35:45 +08:00
|
|
|
* Allow building in directories containing spaces
|
|
|
|
|
|
|
|
|
|
This is probably not possible because 'gmake' and other compiler tools
|
|
|
|
|
do not fully support quoting of paths with spaces.
|
|
|
|
|
|
2005-05-10 11:21:58 +08:00
|
|
|
* Fix sgmltools so PDFs can be generated with bookmarks
|
2005-09-03 04:11:34 +08:00
|
|
|
* Use UTF8 encoding for NLS messages so all server encodings can
|
|
|
|
|
read them properly
|
2005-09-17 01:37:10 +08:00
|
|
|
* Update Bonjour to work with newer cross-platform SDK
|
2007-02-14 02:08:39 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php
|
2007-02-14 07:23:11 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
|
2007-02-14 02:08:39 +08:00
|
|
|
|
2006-03-01 03:48:03 +08:00
|
|
|
* Split out libpq pgpass and environment documentation sections to make
|
|
|
|
|
it easier for non-developers to find
|
2006-07-30 09:48:40 +08:00
|
|
|
* Consider detoasting keys before sorting
|
2006-05-30 18:21:12 +08:00
|
|
|
* Consider GnuTLS if OpenSSL license becomes a problem
|
|
|
|
|
|
2006-06-09 00:07:23 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php
|
2006-12-29 04:51:13 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2006-10-03 07:26:02 +08:00
|
|
|
* Use strlcpy() rather than our StrNCpy() macro
|
2006-10-03 07:23:32 +08:00
|
|
|
|
2006-10-03 08:03:54 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php
|
|
|
|
|
|
2006-12-15 21:28:54 +08:00
|
|
|
* Consider changing documentation format from SGML to XML
|
2006-12-15 11:01:20 +08:00
|
|
|
|
2006-12-15 21:28:54 +08:00
|
|
|
http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php
|
2006-12-15 11:01:20 +08:00
|
|
|
|
2007-02-07 00:44:14 +08:00
|
|
|
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h
|
|
|
|
|
* Consider making NAMEDATALEN more configurable in future releases
|
2007-08-28 11:00:36 +08:00
|
|
|
* Update our code to handle 64-bit timezone files to match the zic
|
2007-02-14 01:03:16 +08:00
|
|
|
source code, which now uses them
|
2007-05-13 06:10:40 +08:00
|
|
|
* Have configure choose integer datetimes by default
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
|
2006-12-15 11:01:20 +08:00
|
|
|
|
2007-05-18 09:22:09 +08:00
|
|
|
* -Fix problem with excessive logging during SSL disconnection
|
2007-05-18 06:42:54 +08:00
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php
|
|
|
|
|
|
2007-05-18 07:42:33 +08:00
|
|
|
* Support scoped IPv6 addresses
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php
|
|
|
|
|
|
2007-05-31 04:26:06 +08:00
|
|
|
* Consider allowing 64-bit integers and floats to be passed by value on
|
|
|
|
|
64-bit platforms
|
|
|
|
|
|
|
|
|
|
Also change 32-bit floats (float4) to be passed by value at the same
|
|
|
|
|
time.
|
|
|
|
|
|
2007-05-31 04:00:35 +08:00
|
|
|
|
2006-06-15 01:59:33 +08:00
|
|
|
|
2004-10-09 00:28:32 +08:00
|
|
|
* Win32
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2004-10-09 00:28:32 +08:00
|
|
|
o Remove configure.in check for link failure when cause is found
|
|
|
|
|
o Remove readdir() errno patch when runtime/mingwex/dirent.c rev
|
|
|
|
|
1.4 is released
|
|
|
|
|
o Remove psql newline patch when we find out why mingw outputs an
|
|
|
|
|
extra newline
|
|
|
|
|
o Allow psql to use readline once non-US code pages work with
|
|
|
|
|
backslashes
|
2004-10-09 09:29:01 +08:00
|
|
|
o Re-enable timezone output on log_line_prefix '%t' when a
|
|
|
|
|
shorter timezone string is available
|
2004-12-03 07:11:30 +08:00
|
|
|
o Fix problem with shared memory on the Win32 Terminal Server
|
2006-06-09 00:07:23 +08:00
|
|
|
o Improve signal handling
|
|
|
|
|
|
2005-09-27 23:18:13 +08:00
|
|
|
http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
|
2006-06-09 00:07:23 +08:00
|
|
|
|
2007-02-20 00:36:17 +08:00
|
|
|
o -Add long file support for binary pg_dump output
|
2007-02-20 23:21:42 +08:00
|
|
|
|
2005-07-31 11:08:35 +08:00
|
|
|
|
2003-02-18 10:49:30 +08:00
|
|
|
* Wire Protocol Changes
|
2005-07-05 01:43:42 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
o Allow dynamic character set handling
|
2003-02-18 10:49:30 +08:00
|
|
|
o Add decoded type, length, precision
|
2004-08-01 13:15:58 +08:00
|
|
|
o Use compression?
|
Cleaups:
< * Allow GRANT/REVOKE permissions to be given to all schema objects with one
> * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
60c60
< specifications. This is because new databases are created by copying
> specifications. This is because new databases are created by copying
63c63
< directory would create a new database with tables that had incorrect
> directory would create a new database with tables that had incorrect
72c72
<
>
85c85
< By not showing commented-out variables, we discourage people from
> By not showing commented-out variables, we discourage people from
91c91
< * Allow point-in-time recovery to archive partially filled write-ahead
> * Allow point-in-time recovery to archive partially filled write-ahead
102c102
< Currently all schemas are owned by the super-user because they are
> Currently all schemas are owned by the super-user because they are
128c128
< * Allow INET subnet tests with non-constants to be indexed
> * Allow INET subnet tests using non-constants to be indexed
143,144c143,144
< * Allow to_char to print localized month names
< * Allow functions to have a search path specified at creation time
> * Allow to_char() to print localized month names
> * Allow functions to have a schema search path specified at creation time
146c146
< * Add GUC variable to allow output of interval values in ISO8601 format
> * Add a GUC variable to allow output of interval values in ISO8601 format
154,155c154,155
< * Prevent inet cast to cidr if the unmasked bits are not zero, or
< zero bits
> * Prevent INET cast to CIDR if the unmasked bits are not zero, or
> zero the bits
158c158
< o Allow nulls in arrays
> o Allow NULLs in arrays
160,161c160,161
< o Delay resolution of array expression type so assignment coercion
< can be performed on empty array expressions
> o Delay resolution of array expression's data type so assignment
> coercion can be performed on empty array expressions
218,219c218,219
< key, foreign key [inheritance]
< * UNIQUE INDEX on base column not honored on inserts/updates from
> key, foreign key
> * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
221c221
< (dup) should fail [inheritance]
> (dup) should fail
246c246
< * Fetch heap pages matching index entries in sequential order [performance]
> * Fetch heap pages matching index entries in sequential order
307c307
< functionality in DELETE. It's been agreed that the keyword should
> functionality in DELETE. It's been agreed that the keyword should
318c318
< * Allow PREPARE to automatically determine parameter types based on the SQL
> * Allow PREPARE to automatically determine parameter types based on the SQL
340,342d339
< * Allow CREATE TABLE foo (f1 INT CHECK (f1 > 0) CHECK (f1 < 10)) to work
< by searching for non-conflicting constraint names, and prefix with
< table name?
347c344
< new database.
> a new database.
350,351d346
< * Ignore temporary tables from other sessions when processing
< inheritance?
354,355c349,351
< * Add a session mode to warn about non-standard SQL usage in queries
< * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules, triggers?)
> * Add a GUC variable to warn about non-standard SQL usage in queries
> * Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
> triggers?)
357,359c353,356
< * Add NOVICE output level for helpful messages like automatic sequence/index creation
< * Add COMMENT ON for all cluster global objects (users, groups,
< databases and tablespaces)
> * Add NOVICE output level for helpful messages like automatic sequence/index
> creation
> * Add COMMENT ON for all cluster global objects (users, groups, databases
> and tablespaces)
363c360
< When enabled, this would allow errors in multi-statement transactions
> When enabled, this would allow errors in multi-statement transactions
417c414
< o Allow COPY to optionally include column headings as the first line
> o Allow COPY to optionally include column headings in the first line
450c447
<
>
462c459
< o Handle references to temporary tables that are created, destroyed,
> o Handle references to temporary tables that are created, destroyed,
464c461
<
>
469d465
< o Improve PL/PgSQL exception handling using savepoints
488c484
<
>
503d498
<
518c513
< o Add pg_dumpall custom format dumps.
> o Add pg_dumpall custom format dumps.
520c515
< This is probably best done by combining pg_dump and pg_dumpall
> This is probably best done by combining pg_dump and pg_dumpall
532d526
< o Improve error handling (?)
555c549
< Adding shared locks requires recording the table/rows numbers in a
> Adding shared locks requires recording the table/rows numbers in a
643c637
< Posix_fadvise() can control both sequential/random file caching and
> Posix_fadvise() can control both sequential/random file caching and
703c697
< from distributted.net, http://www1.distributed.net/source,
> from distributted.net, http://www1.distributed.net/source,
729c723
< * Add connection pooling [pool]
> * Add connection pooling
755d748
<
759c752
<
>
768c761
< so an abrupt operating system restart might lose a few seconds of
> so an abrupt operating system restart might lose a few seconds of
785c778
< * Add utility to compute accurate random_page_cost value
> * Create utility to compute accurate random_page_cost value
787,789d779
< * Allow sorting, temp files, temp tables to use multiple work directories
<
< This allows the I/O load to be spread across multiple disk drives.
795a786
>
808,809c799,800
<
< * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap]
>
> * Use mmap() rather than SYSV shared memory or to write WAL files (?)
812,813c803,804
< portability issues. Anonymous mmap (or mmap to /dev/zero) is required
< to prevent I/O overhead.
> portability issues. Anonymous mmap (or mmap to /dev/zero) is required
> to prevent I/O overhead.
817,819c808,810
< 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,
> 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,
821c812
< way to _prevent_ I/O to disk from the dirty shared buffers so changes
> way to _prevent_ I/O to disk from the dirty shared buffers so changes
826c817
< tuple overhead
> per-tuple overhead
829,831c820,822
< This would involve using multiple threads or processes to do optimization,
< sorting, or execution of single query. The major advantage of such a
< feature would be to allow multiple CPUs to work together to process a
> This would involve using multiple threads or processes to do optimization,
> sorting, or execution of single query. The major advantage of such a
> feature would be to allow multiple CPUs to work together to process a
834c825
< * Research the use of larger pages sizes
> * Research the use of larger page sizes
842a834
> * Move some /contrib modules out to their own project sites
845d836
< * Improve access-permissions check on data directory in Cygwin (Tom)
847,848c838
< * Clarify use of 'application' and 'command' tags in SGML docs
< * Better document ability to build only certain interfaces (Marc)
> * Improve documentation to build only interfaces (Marc)
852,853d841
< * Research interaction of setitimer() and sleep() used by statement_timeout
< * Rename /scripts directory because they are all C programs now
856,857d843
< * Allow binaries to be statically linked so they are more easily relocated
< * Move some /contrib modules out to their own project sites
862c848
< o Remove per-backend parameter file and move into shared memory?
> o Remove per-backend parameter file and move into shared memory
877,878c863,864
< o Update clients to use data types, typmod, schema.table.column names of
< result sets using new query protocol
> o Update clients to use data types, typmod, schema.table.column names
> of result sets using new query protocol
900d885
< * Kris is Kris Jurka
910c895
< * Simon is Simon Riggs
> * Simon is Simon Riggs <simon@2ndquadrant.com>
913d897
< * Teodor is
2004-11-11 11:59:14 +08:00
|
|
|
o 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 21:36:36 +08:00
|
|
|
of result sets using new statement protocol
|
2003-02-18 10:49:30 +08:00
|
|
|
|
2004-08-01 13:15:58 +08:00
|
|
|
|
2006-10-02 22:00:04 +08:00
|
|
|
Exotic Features
|
|
|
|
|
===============
|
|
|
|
|
|
|
|
|
|
* Add pre-parsing phase that converts non-ISO syntax to supported
|
|
|
|
|
syntax
|
|
|
|
|
|
|
|
|
|
This could allow SQL written for other databases to run without
|
|
|
|
|
modification.
|
|
|
|
|
|
|
|
|
|
* Allow plug-in modules to emulate features from other databases
|
|
|
|
|
* Allow statements across databases or servers with transaction
|
|
|
|
|
semantics
|
|
|
|
|
|
|
|
|
|
This can be done using dblink and two-phase commit.
|
|
|
|
|
|
|
|
|
|
* Add the features of packages
|
|
|
|
|
|
|
|
|
|
o Make private objects accessible only to objects in the same schema
|
|
|
|
|
o Allow current_schema.objname to access current schema objects
|
|
|
|
|
o Add session variables
|
|
|
|
|
o Allow nested schemas
|
|
|
|
|
|
|
|
|
|
* Consider allowing control of upper/lower case folding of unquoted
|
|
|
|
|
identifiers
|
|
|
|
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php
|
2006-11-15 06:26:49 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
|
2006-10-02 22:00:04 +08:00
|
|
|
|
|
|
|
|
|
2006-08-10 00:35:51 +08:00
|
|
|
Features We Do _Not_ Want
|
|
|
|
|
=========================
|
|
|
|
|
|
2006-08-24 02:32:02 +08:00
|
|
|
* All backends running as threads in a single process (not wanted)
|
2006-08-10 00:35:51 +08:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2006-08-24 02:32:02 +08:00
|
|
|
* Optimizer hints (not wanted)
|
2006-08-10 00:35:51 +08:00
|
|
|
|
|
|
|
|
Optimizer hints are used to work around problems in the optimizer. We
|
|
|
|
|
would rather have the problems reported and fixed.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-08-10 00:35:51 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
|
2006-10-13 05:40:15 +08:00
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php
|
2006-08-10 00:35:51 +08:00
|
|
|
|
2006-08-24 02:32:02 +08:00
|
|
|
* Allow AS in "SELECT col AS label" to be optional (not wanted)
|
|
|
|
|
|
|
|
|
|
Because we support postfix operators, it isn't possible to make AS
|
|
|
|
|
optional and continue to use bison.
|
2007-07-17 08:07:54 +08:00
|
|
|
|
2006-08-24 02:32:02 +08:00
|
|
|
http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
|
|
|
|
|
|
2006-12-15 23:40:52 +08:00
|
|
|
* Embedded server (not wanted)
|
|
|
|
|
|
2006-12-17 11:57:07 +08:00
|
|
|
While PostgreSQL clients runs fine in limited-resource environments, the
|
2006-12-15 23:40:52 +08:00
|
|
|
server requires multiple processes and a stable pool of resources to
|
2007-08-28 11:00:36 +08:00
|
|
|
run reliabily and efficiently. Stripping down the PostgreSQL server
|
|
|
|
|
to run in the same process address space as the client application
|
2006-12-15 23:40:52 +08:00
|
|
|
would add too much complexity and failure cases.
|
