3 Current maintainer: Bruce Momjian (bruce@momjian.us)
4 Last updated: Tue Mar 11 15:31:58 EDT 2008
6 The most recent version of this document can be viewed at
7 http://www.postgresql.org/docs/faqs.TODO.html.
9 #A hyphen, "-", marks changes that will appear in the upcoming 8.3 release.#
10 #A percent sign, "%", marks items that are easier to implement.#
12 Bracketed items, "[]", have more detail.
14 This list contains all known PostgreSQL bugs and feature requests. If
15 you would like to work on an item, please read the Developer's FAQ
16 first. There is also a developer's wiki at
17 http://developer.postgresql.org.
23 * Allow administrators to safely terminate individual sessions either
24 via an SQL function or SIGTERM
26 Lock table corruption following SIGTERM of an individual backend
27 has been reported in 8.0. A possible cause was fixed in 8.1, but
28 it is unknown whether other problems exist. This item mostly
29 requires additional testing rather than of writing any new code.
31 http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
32 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
34 * Check for unreferenced table files created by transactions that were
35 in-progress when the server terminated abruptly
37 http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php
39 * Set proper permissions on non-system schemas during db creation
41 Currently all schemas are owned by the super-user because they are copied
42 from the template1 database. However, since all objects are inherited
43 from the template database, it is not clear that setting schemas to the db
46 * Add function to report the time of the most recent server reload
47 * Allow statistics collector information to be pulled from the collector
48 process directly, rather than requiring the collector to write a
49 filesystem file twice a second?
50 * Allow statistics last vacuum/analyze execution times to be displayed
51 without requiring stats_row_level to be enabled
52 * Allow log_min_messages to be specified on a per-module basis
54 This would allow administrators to see more detailed information from
55 specific sections of the backend, e.g. checkpoints, autovacuum, etc.
56 Another idea is to allow separate configuration files for each module,
57 or allow arbitrary SET commands to be passed to them.
59 * Simplify ability to create partitioned tables
61 This would allow creation of partitioned tables without requiring
62 creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints
63 for rapid partition selection. Options could include range and hash
66 http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php
67 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php
69 * Allow auto-selection of partitioned tables for min/max() operations
70 * Allow more complex user/database default GUC settings
72 Currently ALTER USER and ALTER DATABASE support per-user and
73 per-database defaults. Consider adding per-user-and-database
74 defaults so things like search_path can be defaulted for a
75 specific user connecting to a specific database.
77 * Allow custom variable classes that can restrict who can set the values
79 http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
81 * Implement the SQL standard mechanism whereby REVOKE ROLE revokes only
82 the privilege granted by the invoking role, and not those granted
85 http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php
87 * Allow SSL authentication/encryption over unix domain sockets
89 http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php
91 * Allow client certificate names to be checked against the client
94 This is already implemented in
95 libpq/fe-secure.c::verify_peer_name_matches_certificate() but the code
100 o Allow pg_hba.conf to specify host names along with IP addresses
102 Host name lookup could occur when the postmaster reads the
103 pg_hba.conf file, or when the backend starts. Another
104 solution would be to reverse lookup the connection IP and
105 check that hostname against the host names in pg_hba.conf.
106 We could also then check that the host name maps to the IP
109 o %Allow postgresql.conf file values to be changed via an SQL
110 API, perhaps using SET GLOBAL
111 o Allow the server to be stopped/restarted via an SQL API
112 o Issue a warning if a change-on-restart-only postgresql.conf value
113 is modified and the server config files are reloaded
118 o Allow a database in tablespace t1 with tables created in
119 tablespace t2 to be used as a template for a new database created
120 with default tablespace t2
122 Currently all objects in the default database tablespace must
123 have default tablespace specifications. This is because new
124 databases are created by copying directories. If you mix default
125 tablespace tables and tablespace-specified tables in the same
126 directory, creating a new database from such a mixed directory
127 would create a new database with tables that had incorrect
128 explicit tablespaces. To fix this would require modifying
129 pg_class in the newly copied database, which we don't currently
132 o Allow reporting of which objects are in which tablespaces
134 This item is difficult because a tablespace can contain objects
135 from multiple databases. There is a server-side function that
136 returns the databases which use a specific tablespace, so this
137 requires a tool that will call that function and connect to each
138 database to find the objects in each database for that tablespace.
140 o Allow WAL replay of CREATE TABLESPACE to work when the directory
141 structure on the recovery computer is different from the original
143 o Allow per-tablespace quotas
146 * Point-In-Time Recovery (PITR)
148 o Allow a warm standby system to also allow read-only statements
151 http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
153 o %Create dump tool for write-ahead logs for use in determining
154 transaction id for point-in-time recovery
156 This is useful for checking PITR recovery.
158 o Allow recovery.conf to support the same syntax as
159 postgresql.conf, including quoting
161 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
167 * Change NUMERIC to enforce the maximum precision
168 * Reduce storage space for small NUMERICs
170 http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php
171 http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php
173 * Fix data types where equality comparison isn't intuitive, e.g. box
174 * Add support for public SYNONYMs
176 http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
178 * Fix CREATE CAST on DOMAINs
180 http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php
181 http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php
183 * Add support for SQL-standard GENERATED/IDENTITY columns
185 http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
186 http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
187 http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php
188 http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
189 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php
191 * Improve XML support
193 http://developer.postgresql.org/index.php/XML_Support
195 * Consider placing all sequences in a single table, or create a system
198 http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
200 * Allow the UUID type to accept non-standard formats
202 http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php
204 * Allow text search dictionary to filter out only stop words
206 http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php
208 * Consider a function-based API for '@@' full text searches
210 http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php
215 o Allow infinite dates and intervals just like infinite timestamps
216 o Merge hardwired timezone names with the TZ database; allow either
217 kind everywhere a TZ name is currently taken
218 o Allow TIMESTAMP WITH TIME ZONE to store the original timezone
219 information, either zone name or offset from UTC [timezone]
221 If the TIMESTAMP value is stored with a time zone name, interval
222 computations should adjust based on the time zone rules.
224 o Fix SELECT '0.01 years'::interval, '0.01 months'::interval
225 o Add a GUC variable to allow output of interval values in ISO8601
227 o Have timestamp subtraction not call justify_hours()?
229 http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php
231 o Improve timestamptz subtraction to be DST-aware
233 Currently subtracting one date from another that crosses a
234 daylight savings time adjustment can return '1 day 1 hour', but
235 adding that back to the first date returns a time one hour in
236 the future. This is caused by the adjustment of '25 hours' to
237 '1 day 1 hour', and '1 day' is the same time the next day, even
238 if daylight savings adjustments are involved.
240 o Fix interval display to support values exceeding 2^31 hours
241 o Add overflow checking to timestamp and interval arithmetic
242 o Extend timezone code to allow 64-bit values so we can
243 represent years beyond 2038
245 http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php
247 o Use LC_TIME for localized weekday/month names, rather than
250 http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
252 o Add ISO INTERVAL handling
254 http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
255 http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php
257 o Support ISO INTERVAL syntax if units cannot be determined from
258 the string, and are supplied after the string
260 The SQL standard states that the units after the string
261 specify the units of the string, e.g. INTERVAL '2' MINUTE
262 should return '00:02:00'. The current behavior has the units
263 restrict the interval value to the specified unit or unit
264 range, INTERVAL '70' SECOND returns '00:00:10'.
266 For syntax that isn't uniquely ISO or PG syntax, like '1' or
267 '1:30', treat as ISO if there is a range specification clause,
268 and as PG if there no clause is present, e.g. interpret '1:30'
269 MINUTE TO SECOND as '1 minute 30 seconds', and interpret
270 '1:30' as '1 hour, 30 minutes'.
272 This makes common cases like SELECT INTERVAL '1' MONTH
273 SQL-standard results. The SQL standard supports a limited
274 number of unit combinations and doesn't support unit names in
275 the string. The PostgreSQL syntax is more flexible in the
276 range of units supported, e.g. PostgreSQL supports '1 year 1
277 hour', while the SQL standard does not.
279 o Add support for year-month syntax, INTERVAL '50-6' YEAR
281 o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1
282 year' AS INTERVAL MONTH), and this should return '12 months'
283 o Round or truncate values to the requested precision, e.g.
284 INTERVAL '11 months' AS YEAR should return one or zero
285 o Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
290 o Delay resolution of array expression's data type so assignment
291 coercion can be performed on empty array expressions
292 o Add support for arrays of domains
294 http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php
296 o Allow single-byte header storage for array elements
301 o Improve vacuum of large objects, like contrib/vacuumlo?
302 o Add security checking for large objects
303 o Auto-delete large objects when referencing row is deleted
305 contrib/lo offers this functionality.
307 o Allow read/write into TOAST values like large objects
309 This requires the TOAST column to be stored EXTERNAL.
311 o Add API for 64-bit large object access
313 http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
317 * Add locale-aware MONEY type, and support multiple currencies
319 http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
320 http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
322 * MONEY dumps in a locale-specific format making it difficult to
323 restore to a system with a different locale
324 * Allow MONEY to be easily cast to/from other numeric data types
330 * Allow INET subnet tests using non-constants to be indexed
331 * Allow to_date() and to_timestamp() accept localized month names
332 * Fix to_date()-related functions to consistently issue errors
334 http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
336 * Add missing parameter handling in to_char()
338 http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php
340 * Allow substring/replace() to get/set bit values
341 * Allow to_char() on interval values to accumulate the highest unit
344 Some special format flag would be required to request such
345 accumulation. Such functionality could also be added to EXTRACT.
346 Prevent accumulation that crosses the month/day boundary because of
347 the uneven number of days in a month.
349 o to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65
350 o to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
351 o to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
352 o to_char(INTERVAL '3 years 5 months','MM') => 41
354 * Implement inlining of set-returning functions defined in SQL
355 * Allow SQL-language functions to return results from RETURNING queries
357 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
359 * Allow SQL-language functions to reference parameters by parameter name
361 Currently SQL-language functions can only refer to dollar parameters,
364 * Add SPI_gettypmod() to return the typemod for a TupleDesc
365 * Enforce typmod for function inputs, function results and parameters for
366 spi_prepare'd statements called from PLs
368 http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php
370 * Allow holdable cursors in SPI
371 * Tighten function permission checks
373 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php
375 * Fix IS OF so it matches the ISO specification, and add documentation
377 http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php
378 http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
380 * Add missing operators for geometric data types
382 Some geometric types do not have the full suite of geometric operators,
385 * Implement Boyer-Moore searching in strpos()
387 http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php
389 * Prevent malicious functions from being executed with the permissions
390 of unsuspecting users
392 Index functions are safe, so VACUUM and ANALYZE are safe too.
393 Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
394 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php
396 * Reduce memory usage of aggregates in set returning functions
398 http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php
400 * Add temporal versions of generate_series()
402 http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php
406 Multi-Language Support
407 ======================
409 * Add NCHAR (as distinguished from ordinary varchar),
410 * Allow locale to be set at database creation
412 Currently locale can only be set during initdb. No global tables have
413 locale-aware columns. However, the database template used during
414 database creation might have locale-aware indexes. The indexes would
415 need to be reindexed to match the new locale.
417 * Allow encoding on a per-column basis optionally using the ICU library:
419 Right now only one encoding is allowed per database. [locale]
421 http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
422 http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php
423 http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php
424 http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php
426 * Add CREATE COLLATE? [locale]
427 * Support multiple simultaneous character sets, per SQL92
428 * Improve UTF8 combined character handling?
429 * Add octet_length_server() and octet_length_client()
430 * Make octet_length_client() the same as octet_length()?
431 * Fix problems with wrong runtime encoding conversion for NLS message files
432 * Add URL to more complete multi-byte regression tests
434 http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
436 * Fix ILIKE and regular expressions to handle case insensitivity
437 properly in multibyte encodings
439 http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
440 http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
442 * Set client encoding based on the client operating system encoding
444 Currently client_encoding is set in postgresql.conf, which
445 defaults to the server encoding.
446 http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php
453 * Automatically create rules on views so they are updateable, per SQL99
455 We can only auto-create rules for simple views. For more complex
456 cases users will still have to write rules manually.
458 http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php
459 http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php
461 * Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
462 * Allow NOTIFY in rules involving conditionals
463 * Allow VIEW/RULE recompilation when the underlying tables change
465 Another issue is whether underlying table changes should be reflected
466 in the view, e.g. should SELECT * show additional columns if they
467 are added after the view is created.
469 * Make it possible to use RETURNING together with conditional DO INSTEAD
470 rules, such as for partitioning setups
472 http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
474 * Add the ability to automatically create materialized views
476 Right now materialized views require the user to create triggers on the
477 main table to keep the summary table current. SQL syntax should be able
478 to manager the triggers and summary table automatically. A more
479 sophisticated implementation would automatically retrieve from the
480 summary table when the main table is referenced, if possible.
487 * Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
488 * Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
489 * %Allow SET CONSTRAINTS to be qualified by schema/table name
490 * %Add a separate TRUNCATE permission
492 Currently only the owner can TRUNCATE a table because triggers are not
493 called, and the table is locked in exclusive mode.
495 * Allow PREPARE of cursors
496 * Allow finer control over the caching of prepared query plans
498 Currently queries prepared via the libpq API are planned on first
499 execute using the supplied parameters --- allow SQL PREPARE to do the
500 same. Also, allow control over replanning prepared queries either
501 manually or automatically when statistics for execute parameters
502 differ dramatically from those used during planning.
504 * Improve logging of prepared transactions recovered during startup
506 http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
508 * Allow LISTEN/NOTIFY to store info in memory rather than tables?
510 Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
511 such information in memory would improve performance.
513 * Add optional textual message to NOTIFY
515 This would allow an informational message to be added to the notify
516 message, perhaps indicating the row modified or other custom
519 * Allow multiple identical NOTIFY events to always be communicated to the
520 client, rather than sent as a single notification to the listener
522 http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
524 * Add a GUC variable to warn about non-standard SQL usage in queries
525 * Add SQL-standard MERGE command, typically used to merge two tables
528 This is similar to UPDATE, then for unmatched rows, INSERT.
529 Whether concurrent access allows modifications which could cause
530 row loss is implementation independent.
532 * Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
535 To implement this cleanly requires that the table have a unique index
536 so duplicate checking can be easily performed. It is possible to
537 do it without a unique index if we require the user to LOCK the table
540 http://archives.postgresql.org/pgsql-hackers/2005-11/msg00501.php
541 http://archives.postgresql.org/pgsql-hackers/2005-11/msg00536.php
543 * Add NOVICE output level for helpful messages like automatic sequence/index
545 * Add GUC to issue notice about statements that use unjoined tables
546 * Allow EXPLAIN to identify tables that were skipped because of
548 * Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
549 * Enable standard_conforming_strings
550 * Make standard_conforming_strings the default in 8.5?
552 When this is done, backslash-quote should be prohibited in non-E''
553 strings because of possible confusion over how such strings treat
554 backslashes. Basically, '' is always safe for a literal single
555 quote, while \' might or might not be based on the backslash
558 * Simplify dropping roles that have objects in several databases
559 * Allow COMMENT ON to accept an expression rather than just a string
560 * Allow the count returned by SELECT, etc to be represented as an int64
561 to allow a higher range of values
562 * Add SQL99 WITH clause to SELECT
563 * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
565 http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php
566 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php
567 http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php
569 * Add DEFAULT .. AS OWNER so permission checks are done as the table
572 This would be useful for SERIAL nextval() calls and CHECK constraints.
574 * Allow DISTINCT to work in multiple-argument aggregate calls
575 * Add column to pg_stat_activity that shows the progress of long-running
576 commands like CREATE INDEX and VACUUM
577 * Implement SQL:2003 window functions
578 * Improve failure message when DROP DATABASE is used on a database that
579 has prepared transactions
580 * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
582 http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php
583 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php
585 * Increase locking when DROPing objects so dependent objects cannot
586 get dropped while the DROP operation is happening
588 http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php
590 * -Allow AS in "SELECT col AS label" to be optional in certain cases
592 * Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ...
593 RETURNING to supply values to the INSERT
594 http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979
596 * Add comments on system tables/columns using the information in
599 Ideally the information would be pulled from the SGML file
605 o Allow CREATE TABLE AS to determine column lengths for complex
606 expressions like SELECT col1 || col2
608 o Have WITH CONSTRAINTS also create constraint indexes
610 http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
612 o Have CONSTRAINT cname NOT NULL record the contraint name
614 Right now pg_attribute.attnotnull records the NOT NULL status
615 of the column, but does not record the contraint name
620 o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
622 http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php
623 http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php
625 o Research self-referential UPDATEs that see inconsistent row versions
626 in read-committed mode
628 http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
629 http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php
631 o Allow GLOBAL temporary tables to exist as empty by default in
634 http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php
639 o Have ALTER TABLE RENAME rename SERIAL sequence names
641 http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
643 o Have ALTER SEQUENCE RENAME rename the sequence name stored
644 in the sequence table
646 http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php
647 http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php
648 http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
650 o Add ALTER DOMAIN to modify the underlying data type
651 o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
653 http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
655 o %Allow ALTER TABLE to change constraint deferrability and actions
656 o Add missing object types for ALTER ... SET SCHEMA
657 o Allow ALTER TABLESPACE to move to different directories
658 o Allow databases to be moved to different tablespaces
659 o Allow moving system tables to other tablespaces, where possible
661 Currently non-global system tables must be in the default database
662 tablespace. Global system tables can never be moved.
664 o Prevent parent tables from altering or dropping constraints
665 like CHECK that are inherited by child tables unless CASCADE
667 o %Prevent child tables from altering or dropping constraints
668 like CHECK that were inherited from the parent table
669 o Have ALTER INDEX update the name of a constraint using that index
670 o Add ALTER TABLE RENAME CONSTRAINT, update index name also
671 o Allow column display reordering by recording a display,
672 storage, and permanent id for every column?
674 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php
680 o Automatically maintain clustering on a table
682 This might require some background daemon to maintain clustering
683 during periods of low usage. It might also require tables to be only
684 partially filled for easier reorganization. Another idea would
685 be to create a merged heap/index data file so an index lookup would
686 automatically access the heap data too. A third idea would be to
687 store heap rows in hashed groups, perhaps using a user-supplied
689 http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php
691 o %Add default clustering to system tables
693 To do this, determine the ideal cluster index for each system
694 table and set the cluster setting during initdb.
696 o %Add VERBOSE option to report tables as they are processed,
702 o Allow COPY to report error lines and continue
704 This requires the use of a savepoint before each COPY line is
705 processed, with ROLLBACK on COPY failure.
707 o Allow COPY on a newly-created table to skip WAL logging
709 On crash recovery, the table involved in the COPY would
710 be removed or have its heap and index files truncated. One
711 issue is that no other backend should be able to add to
712 the table at the same time, which is something that is
713 currently allowed. This currently is done if the table is
714 created inside the same transaction block as the COPY because
715 no other backends can see the table.
717 o Consider using a ring buffer for COPY FROM
719 http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php
720 http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php
722 o Allow COPY FROM to create index entries in bulk
724 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php
730 o Allow column-level privileges
731 o %Allow GRANT/REVOKE permissions to be applied to all schema objects
734 The proposed syntax is:
735 GRANT SELECT ON ALL TABLES IN public TO phpuser;
736 GRANT SELECT ON NEW TABLES IN public TO phpuser;
738 o Allow GRANT/REVOKE permissions to be inherited by objects based on
741 o Allow SERIAL sequences to inherit permissions from the base table?
746 o Prevent DROP TABLE from dropping a row referenced by its own open
752 o Allow INSERT/UPDATE of the system-generated oid value for a row
753 o In rules, allow VALUES() to contain a mixture of 'old' and 'new'
759 o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
764 Referential Integrity
765 =====================
767 * Add MATCH PARTIAL referential integrity
768 * Change foreign key constraint for array -> element to mean element
770 * Fix problem when cascading referential triggers make changes on
771 cascaded tables, seeing the tables in an intermediate state
773 http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
774 http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
776 * Allow DEFERRABLE and end-of-statement UNIQUE constraints?
778 This would allow UPDATE tab SET col = col + 1 to work if col has
779 a unique index. Currently, uniqueness checks are done while the
780 command is being executed, rather than at the end of the statement
782 http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html
783 http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php
785 * Optimize referential integrity checks
787 http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
788 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php
791 Server-Side Languages
792 =====================
795 o Fix RENAME to work on variables other than OLD/NEW
797 http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php
798 http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php
799 http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
801 o Allow function parameters to be passed by name,
802 get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
803 o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
804 o Allow listing of record column names, and access to
805 record columns via variables, e.g. columns := r.(*),
808 http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
809 http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
810 http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
812 o Add support for SCROLL cursors
813 o Add support for WITH HOLD cursors
814 o Allow row and record variables to be set to NULL constants,
815 and allow NULL tests on such variables
817 Because a row is not scalar, do not allow assignment
818 from NULL-valued scalars.
820 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php
822 o Review handling of MOVE and FETCH
824 http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php
828 o Add table function support to pltcl, plpythonu
829 o Add support for polymorphic arguments and return types to
830 languages other than PL/PgSQL
831 o Add capability to create and call PROCEDURES
832 o Add support for OUT and INOUT parameters to languages other
834 o Add PL/PythonU tracebacks
836 http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php
838 o Allow data to be passed in native language formats, rather
841 http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
848 * Have pg_ctl look at PGHOST in case it is a socket directory?
849 * Allow pg_ctl to work properly with configuration files located outside
852 pg_ctl can not read the pid file because it isn't located in the
853 config directory but in the PGDATA directory. The solution is to
854 allow pg_ctl to read and understand postgresql.conf to find the
855 data_directory value.
857 * Add a function like pg_get_indexdef() that report more detailed index
860 http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php
864 o Have psql show current values for a sequence
865 o Move psql backslash database information into the backend, use
866 mnemonic commands? [psql]
868 This would allow non-psql clients to pull the same information out
869 of the database as psql.
871 o Fix psql's \d commands more consistent
873 http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
874 http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
876 o Consistently display privilege information for all objects in psql
877 o Add auto-expanded mode so expanded output is used if the row
878 length is wider than the screen width.
880 Consider using auto-expanded mode for backslash commands like \df+.
882 o Prevent tab completion of SET TRANSACTION from querying the
883 database and therefore preventing the transaction isolation
884 level from being set.
886 Currently SET <tab> causes a database lookup to check all
887 supported session variables. This query causes problems
888 because setting the transaction isolation level must be the
889 first statement of a transaction.
891 o Add a \set variable to control whether \s displays line numbers
893 Another option is to add \# which lists line numbers, and
894 allows command execution.
896 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
898 o Prevent escape string warnings when object names have
901 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php
903 o Have \d show foreign keys that reference a table's primary key
905 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php
907 o Have \d show child tables that inherit from the specified parent
908 o Have \l+ show database size, if permissions allow
910 Ideally it will not generate an error for invalid permissions
914 * pg_dump / pg_restore
915 o %Add dumping of comments on index columns and composite type columns
916 o %Add full object name to the tag field. eg. for operators we need
917 '=(integer, integer)', instead of just '='.
918 o Add pg_dumpall custom format dumps?
919 o Allow selection of individual object(s) of all types, not just
921 o In a selective dump, allow dumping of an object and all its
923 o Add options like pg_restore -l and -L to pg_dump
924 o Stop dumping CASCADE on DROP TYPE commands in clean mode
925 o Allow pg_dump --clean to drop roles that own objects or have
927 o Change pg_dump so that a comment on the dumped database is
928 applied to the loaded database, even if the database has a
929 different name. This will require new backend syntax, perhaps
930 COMMENT ON CURRENT DATABASE.
931 o Remove unnecessary function pointer abstractions in pg_dump source
933 o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
934 multiple objects simultaneously
936 The difficulty with this is getting multiple dump processes to
937 produce a single dump output file. It also would require
938 several sessions to share the same snapshot.
939 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
941 o Allow pg_restore to utilize multiple CPUs and I/O channels by
942 restoring multiple objects simultaneously
944 This might require a pg_restore flag to indicate how many
945 simultaneous operations should be performed. Only pg_dump's
946 -Fc format has the necessary dependency information.
947 http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php
949 o To better utilize resources, allow pg_restore to check foreign
950 keys simultaneously, where possible
951 o Allow pg_restore to create all indexes of a table
952 concurrently, via a single heap scan
954 This requires a pg_dump -Fc file because that format contains
955 the required dependency information.
956 http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
958 o Allow pg_restore to load different parts of the COPY data
960 o Prevent pg_dump/pg_restore from being affected by
963 Using psql to restore a pg_dump dump is also affected.
969 Document differences between ecpg and the SQL standard and
970 information about the Informix-compatibility module.
972 o Solve cardinality > 1 for input descriptors / variables?
973 o Add a semantic check level, e.g. check if a table really exists
974 o fix handling of DB attributes that are arrays
975 o Use backend PREPARE/EXECUTE facility for ecpg where possible
977 o Fix nested C comments
978 o %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified
979 o Make SET CONNECTION thread-aware, non-standard?
980 o Allow multidimensional arrays
981 o Add internationalized message strings
982 o Implement COPY FROM STDIN
986 o Add PQescapeIdentifierConn()
987 o Prevent PQfnumber() from lowercasing unquoted the column name
989 PQfnumber() should never have been doing lowercasing, but
990 historically it has so we need a way to prevent it
992 o Allow statement results to be automatically batched to the client
994 Currently all statement results are transferred to the libpq
995 client before libpq makes the results available to the
996 application. This feature would allow the application to make
997 use of the first result rows while the rest are transferred, or
998 held on the server waiting for them to be requested by libpq.
999 One complexity is that a statement like SELECT 1/col could error
1000 out mid-way through the result set.
1002 o Consider disallowing multiple queries in PQexec() as an
1003 additional barrier to SQL injection attacks
1005 http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php
1007 o Add PQexecf() that allows complex parameter substitution
1009 http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php
1011 o Add SQLSTATE severity to PGconn return status
1013 http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php
1019 * Add deferred trigger queue file
1021 Right now all deferred trigger information is stored in backend
1022 memory. This could exhaust memory for very large trigger queues.
1023 This item involves dumping large queues into files.
1025 * Allow triggers to be disabled in only the current session.
1027 This is currently possible by starting a multi-statement transaction,
1028 modifying the system tables, performing the desired SQL, restoring the
1029 system tables, and committing the transaction. ALTER TABLE ...
1030 TRIGGER requires a table lock so it is not ideal for this usage.
1032 * With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
1034 If the dump is known to be valid, allow foreign keys to be added
1035 without revalidating the data.
1037 * Allow statement-level triggers to access modified rows
1038 * Support triggers on columns
1040 http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php
1042 * Allow AFTER triggers on system tables
1044 System tables are modified in many places in the backend without going
1045 through the executor and therefore not causing triggers to fire. To
1046 complete this item, the functions that modify system tables will have
1049 * Tighten trigger permission checks
1051 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
1053 * Allow BEFORE INSERT triggers on views
1055 http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php
1057 * Add ability to trigger on TRUNCATE
1059 http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php
1066 * Add UNIQUE capability to non-btree indexes
1067 * Prevent index uniqueness checks when UPDATE does not modify the column
1069 Uniqueness (index) checks are done when updating a column even if the
1070 column is not modified by the UPDATE.
1072 * Allow the creation of on-disk bitmap indexes which can be quickly
1073 combined with other bitmap indexes
1075 Such indexes could be more compact if there are only a few distinct values.
1076 Such indexes can also be compressed. Keeping such indexes updated can be
1079 http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
1080 http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
1082 * Allow accurate statistics to be collected on indexes with more than
1083 one column or expression indexes, perhaps using per-index statistics
1085 http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php
1086 http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php
1088 * Consider increasing the number of default statistics target, and
1089 reduce statistics target overhead
1091 Also consider having a larger statistics target for indexed columns
1092 and expression indexes
1093 http://archives.postgresql.org/pgsql-general/2007-05/msg01228.php
1096 * Consider compressing indexes by storing key values duplicated in
1097 several rows as a single index entry
1099 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php
1100 http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
1101 http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
1102 http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
1104 * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
1106 This is difficult because you must upgrade to an exclusive table lock
1107 to replace the existing index file. CREATE INDEX CONCURRENTLY does not
1108 have this complication. This would allow index compaction without
1111 * Allow multiple indexes to be created concurrently, ideally via a
1112 single heap scan, and have pg_restore use it
1118 o Allow inherited tables to inherit indexes, UNIQUE constraints,
1119 and primary/foreign keys
1120 o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
1121 on inherited table, e.g. INSERT INTO inherit_table
1122 (unique_index_col) VALUES (dup) should fail
1124 The main difficulty with this item is the problem of
1125 creating an index that can span multiple tables.
1127 o Allow SELECT ... FOR UPDATE on inherited tables
1128 o Require all CHECK constraints to be inherited
1130 http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
1135 o Add more GIST index support for geometric data types
1136 o Allow GIST indexes to create certain complex index types, like
1137 digital trees (see Aoki)
1142 http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
1144 o Pack hash index buckets onto disk pages more efficiently
1146 Currently only one hash bucket can be stored on a page. Ideally
1147 several hash buckets could be stored on a single page and greater
1148 granularity used for the hash algorithm.
1150 http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php
1152 o Consider sorting hash buckets so entries can be found using a
1153 binary search, rather than a linear scan
1154 o In hash indexes, consider storing the hash value with or instead
1156 o Add WAL logging for crash recovery
1157 o Allow multi-column hash indexes
1158 o During index creation, pre-sort the tuples to improve build speed
1160 http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php
1167 * Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
1169 Ideally this requires a separate test program that can be run
1170 at initdb time or optionally later. Consider O_SYNC when
1173 * Add program to test if fsync has a delay compared to non-fsync
1182 We could use a fixed row count and a +/- count to follow MVCC
1183 visibility rules, or a single cached value could be used and
1184 invalidated if anyone modifies the table. Another idea is to
1185 get a count directly from a unique index, but for this to be
1186 faster than a sequential scan it must avoid access to the heap
1187 to obtain tuple visibility information.
1189 * Provide a way to calculate an "estimated COUNT(*)"
1191 Perhaps by using the optimizer's cardinality estimates or random
1194 http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
1196 * Allow data to be pulled directly from indexes
1198 Currently indexes do not have enough tuple visibility information
1199 to allow data to be pulled from the index without also accessing
1200 the heap. One way to allow this is to set a bit on index tuples
1201 to indicate if a tuple is currently visible to all transactions
1202 when the first valid heap lookup happens. This bit would have to
1203 be cleared when a heap tuple is expired.
1205 Another idea is to maintain a bitmap of heap pages where all rows
1206 are visible to all backends, and allow index lookups to reference
1207 that bitmap to avoid heap lookups, perhaps the same bitmap we might
1208 add someday to determine which heap pages need vacuuming. Frequently
1209 accessed bitmaps would have to be stored in shared memory. One 8k
1210 page of bitmaps could track 512MB of heap pages.
1212 A third idea would be for a heap scan to check if all rows are visible
1213 and if so set a per-table flag which can be checked by index scans.
1214 Any change to the table would have to clear the flag. To detect
1215 changes during the heap scan a counter could be set at the start and
1216 checked at the end --- if it is the same, the table has not been
1217 modified --- any table change would increment the counter.
1219 * Consider automatic caching of statements at various levels:
1222 o Query execute plan
1225 * Consider increasing internal areas when shared buffers is increased
1227 http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
1229 * Consider decreasing the amount of memory used by PrivateRefCount
1231 http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php
1232 http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
1234 * Consider allowing higher priority queries to have referenced buffer
1235 cache pages stay in memory longer
1237 http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php
1244 * Improve speed with indexes
1246 For large table adjustments during VACUUM FULL, it is faster to cluster
1247 or reindex rather than update the index. Also, index updates can bloat
1250 http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
1251 http://archives.postgresql.org/pgsql-performance/2007-05/msg00296.php
1253 * Auto-fill the free space map by scanning the buffer cache or by
1254 checking pages written by the background writer
1256 http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php
1257 http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php
1259 * Create a bitmap of pages that need vacuuming
1261 Instead of sequentially scanning the entire table, have the background
1262 writer or some other process record pages that have expired rows, then
1263 VACUUM can look at just those pages rather than the entire table. In
1264 the event of a system crash, the bitmap would probably be invalidated.
1265 One complexity is that index entries still have to be vacuumed, and
1266 doing this without an index scan (by using the heap values to find the
1267 index entry) might be slow and unreliable, especially for user-defined
1270 http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php
1271 http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php
1273 * Allow FSM to return free space toward the beginning of the heap file,
1274 in hopes that empty pages at the end can be truncated by VACUUM
1275 * Allow FSM page return free space based on table clustering, to assist
1276 in maintaining clustering?
1277 * Improve dead row detection during multi-statement transactions usage
1279 http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
1281 * Consider a more compact data representation for dead tuples
1283 http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php
1288 o %Issue log message to suggest VACUUM FULL if a table is nearly
1290 o Improve control of auto-vacuum
1292 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
1294 o Prevent long-lived temporary tables from causing frozen-xid
1295 advancement starvation
1297 The problem is that autovacuum cannot vacuum them to set frozen xids;
1298 only the session that created them can do that.
1299 http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php
1301 o Store per-table autovacuum settings in pg_class.reloptions.
1303 http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php
1304 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php
1306 o Prevent autovacuum from running if an old transaction is still
1307 running from the last vacuum
1309 http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php
1316 * Fix priority ordering of read and write light-weight locks (Neil)
1318 http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php
1319 http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php
1321 * Fix problem when multiple subtransactions of the same outer transaction
1322 hold different types of locks, and one subtransaction aborts
1324 http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php
1325 http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
1326 http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
1327 http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php
1329 * Allow UPDATEs on only non-referential integrity columns not to conflict
1330 with referential integrity locks
1332 http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php
1334 * Add idle_in_transaction_timeout GUC so locks are not held for long
1337 * Improve deadlock detection when a page cleaning lock conflicts
1338 with a shared buffer that is pinned
1340 http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php
1341 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
1342 http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php
1347 Startup Time Improvements
1348 =========================
1350 * Experiment with multi-threaded backend for backend creation [thread]
1352 This would prevent the overhead associated with process creation. Most
1353 operating systems have trivial process creation time compared to
1354 database startup overhead, but a few operating systems (Win32,
1355 Solaris) might benefit from threading. Also explore the idea of
1356 a single session using multiple threads to execute a statement faster.
1363 * Eliminate need to write full pages to WAL before page modification [wal]
1365 Currently, to protect against partial disk page writes, we write
1366 full page images to WAL before they are modified so we can correct any
1367 partial page writes during recovery. These pages can also be
1368 eliminated from point-in-time archive files.
1370 o When off, write CRC to WAL and check file system blocks
1373 If CRC check fails during recovery, remember the page in case
1374 a later CRC for that page properly matches.
1376 o Write full pages during file system write and not when
1377 the page is modified in the buffer cache
1379 This allows most full page writes to happen in the background
1380 writer. It might cause problems for applying WAL on recovery
1381 into a partially-written page, but later the full page will be
1384 * Allow WAL traffic to be streamed to another server for stand-by
1386 * Reduce WAL traffic so only modified values are written rather than
1389 http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
1391 * Allow WAL information to recover corrupted pg_controldata
1393 http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
1395 * Find a way to reduce rotational delay when repeatedly writing
1398 Currently fsync of WAL requires the disk platter to perform a full
1399 rotation to fsync again. One idea is to write the WAL to different
1400 offsets that might reduce the rotational delay.
1402 * Allow WAL logging to be turned off for a table, but the table
1403 might be dropped or truncated during crash recovery [walcontrol]
1405 Allow tables to bypass WAL writes and just fsync() dirty pages on
1406 commit. This should be implemented using ALTER TABLE, e.g. ALTER
1407 TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using
1408 non-default logging should not use referential integrity with
1409 default-logging tables. A table without dirty buffers during a
1410 crash could perhaps avoid the drop/truncate.
1412 * Allow WAL logging to be turned off for a table, but the table would
1413 avoid being truncated/dropped [walcontrol]
1415 To do this, only a single writer can modify the table, and writes
1416 must happen only on new pages so the new pages can be removed during
1417 crash recovery. Readers can continue accessing the table. Such
1418 tables probably cannot have indexes. One complexity is the handling
1419 of indexes on TOAST tables.
1421 * Speed WAL recovery by allowing more than one page to be prefetched
1423 This involves having a separate process that can be told which pages
1424 the recovery process will need in the near future.
1425 http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php
1429 Optimizer / Executor
1430 ====================
1432 * Improve selectivity functions for geometric operators
1433 * Precompile SQL functions to avoid overhead
1434 * Create utility to compute accurate random_page_cost value
1435 * Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
1436 * Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and
1437 actual row counts differ by a specified percentage
1438 * Consider using hash buckets to do DISTINCT, rather than sorting
1440 This would be beneficial when there are few distinct values. This is
1441 already used by GROUP BY.
1443 * Log statements where the optimizer row estimates were dramatically
1444 different from the number of rows actually found?
1445 * Consider compressed annealing to search for query plans
1447 This might replace GEQO, http://sixdemonbag.org/Djinni.
1449 * Improve merge join performance by allowing mark/restore of
1452 http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php
1454 * Consider using a hash for joining to a large IN (VALUES ...) list
1456 http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php
1460 Miscellaneous Performance
1461 =========================
1463 * Do async I/O for faster random read-ahead of data
1465 Async I/O allows multiple I/O requests to be sent to the disk with
1466 results coming back asynchronously.
1468 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php
1469 http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php
1471 * Use mmap() rather than SYSV shared memory or to write WAL files?
1473 This would remove the requirement for SYSV SHM but would introduce
1474 portability issues. Anonymous mmap (or mmap to /dev/zero) is required
1475 to prevent I/O overhead.
1477 * Consider mmap()'ing files into a backend?
1479 Doing I/O to large tables would consume a lot of address space or
1480 require frequent mapping/unmapping. Extending the file also causes
1481 mapping problems that might require mapping only individual pages,
1482 leading to thousands of mappings. Another problem is that there is no
1483 way to _prevent_ I/O to disk from the dirty shared buffers so changes
1484 could hit disk before WAL is written.
1486 * Add a script to ask system configuration questions and tune postgresql.conf
1487 * Consider ways of storing rows more compactly on disk
1489 o Reduce the row header size?
1490 o Consider reducing on-disk varlena length from four bytes to
1491 two because a heap row cannot be more than 64k in length
1493 * Consider increasing NUM_CLOG_BUFFERS
1494 * Consider having the background writer update the transaction status
1495 hint bits before writing out the page
1497 Implementing this requires the background writer to have access to system
1498 catalogs and the transaction status log.
1500 * Consider adding buffers the BGW finds reusable to the free list
1502 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
1504 * Automatically tune bgwriter_delay based on activity rather then using a
1507 http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
1509 * Allow user configuration of TOAST thresholds
1511 http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php
1513 * Allow configuration of backend priorities via the operating system
1515 Though backend priorities make priority inversion during lock
1516 waits possible, research shows that this is not a huge problem.
1518 http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php
1520 * Experiment with multi-threaded backend better resource utilization
1522 This would allow a single query to make use of multiple CPU's or
1523 multiple I/O channels simultaneously. One idea is to create a
1524 background reader that can pre-fetch sequential and index scan
1525 pages needed by other backends. This could be expanded to allow
1526 concurrent reads from multiple devices in a partitioned table.
1528 * Consider increasing the minimum allowed number of shared buffers
1530 http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php
1538 * Add use of 'const' for variables in source tree
1539 * Move some things from contrib into main tree
1540 * %Remove warnings created by -Wcast-align
1541 * Move platform-specific ps status display info from ps_status.c to ports
1542 * Add optional CRC checksum to heap and index pages
1543 * Improve documentation to build only interfaces (Marc)
1544 * Remove or relicense modules that are not under the BSD license, if possible
1545 * Acquire lock on a relation before building a relcache entry for it
1546 * Allow cross-compiling by generating the zic database on the target system
1547 * Improve NLS maintenance of libpgport messages linked onto applications
1548 * Clean up casting in contrib/isn
1550 http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php
1552 * Use UTF8 encoding for NLS messages so all server encodings can
1554 * Update Bonjour to work with newer cross-platform SDK
1556 http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php
1557 http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
1559 * Consider detoasting keys before sorting
1560 * Consider GnuTLS if OpenSSL license becomes a problem
1562 http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php
1563 http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php
1565 * Consider changing documentation format from SGML to XML
1567 http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php
1569 * Consider making NAMEDATALEN more configurable in future releases
1570 * Update our code to handle 64-bit timezone files to match the zic
1571 source code, which now uses them
1572 * Have configure choose integer datetimes by default
1574 http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
1576 * Support scoped IPv6 addresses
1578 http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php
1580 * Consider allowing 64-bit integers and floats to be passed by value on
1583 Also change 32-bit floats (float4) to be passed by value at the same
1590 o Remove configure.in check for link failure when cause is found
1591 o Remove readdir() errno patch when runtime/mingwex/dirent.c rev
1593 o Remove psql newline patch when we find out why mingw outputs an
1595 o Allow psql to use readline once non-US code pages work with
1597 o Fix problem with shared memory on the Win32 Terminal Server
1598 o Improve signal handling
1600 http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
1604 * Wire Protocol Changes
1606 o Allow dynamic character set handling
1607 o Add decoded type, length, precision
1609 o Update clients to use data types, typmod, schema.table.column names
1610 of result sets using new statement protocol
1616 * Add pre-parsing phase that converts non-ISO syntax to supported
1619 This could allow SQL written for other databases to run without
1622 * Allow plug-in modules to emulate features from other databases
1623 * Add features of Oracle-style packages (Pavel)
1625 A package would be a schema with session-local variables,
1626 public/private functions, and initialization functions. It
1627 is also possible to implement these capabilities
1628 in any schema and not use a separate "packages"
1631 http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
1633 * Consider allowing control of upper/lower case folding of unquoted
1636 http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php
1637 http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
1639 * Add autonomous transactions
1641 http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
1645 Features We Do _Not_ Want
1646 =========================
1648 * All backends running as threads in a single process (not wanted)
1650 This eliminates the process protection we get from the current setup.
1651 Thread creation is usually the same overhead as process creation on
1652 modern systems, so it seems unwise to use a pure threaded model.
1654 * Optimizer hints (not wanted)
1656 Optimizer hints are used to work around problems in the optimizer. We
1657 would rather have the problems reported and fixed.
1659 http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php
1660 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php
1661 http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php
1664 Because we support postfix operators, it isn't possible to make AS
1665 optional and continue to use bison.
1666 http://archives.postgresql.org/pgsql-hackers/2003-04/msg00436.php
1668 http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
1670 * Embedded server (not wanted)
1672 While PostgreSQL clients runs fine in limited-resource environments, the
1673 server requires multiple processes and a stable pool of resources to
1674 run reliabily and efficiently. Stripping down the PostgreSQL server
1675 to run in the same process address space as the client application
1676 would add too much complexity and failure cases.