From 4835df303dae1b21c3c334202bea6d698cd38b75 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 5 May 2007 15:40:01 +0000 Subject: [PATCH] Done: < Last updated: Sat May 5 10:47:39 EDT 2007 > Last updated: Sat May 5 11:39:57 EDT 2007 < * Flush cached query plans when the dependent objects change, < when the cardinality of parameters changes dramatically, or > * -Flush cached query plans when the dependent objects change or < < A more complex solution would be to save multiple plans for different < cardinality and use the appropriate plan based on the EXECUTE values. < < * Track dependencies in function bodies and recompile/invalidate < < 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. One complexity is that a function < might itself drop and recreate dependent tables, causing it to < invalidate its own query plan. < < * Invalidate prepared queries, like INSERT, when the table definition > * -Track dependencies in function bodies and recompile/invalidate > * -Invalidate prepared queries, like INSERT, when the table definition --- doc/TODO | 22 +++---------- doc/src/FAQ/TODO.html | 72 +++++++++++++++++++------------------------ 2 files changed, 37 insertions(+), 57 deletions(-) diff --git a/doc/TODO b/doc/TODO index 92f41e7226..d492324b3e 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,8 +1,8 @@ - +z PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat May 5 10:47:39 EDT 2007 +Last updated: Sat May 5 11:39:57 EDT 2007 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -958,22 +958,10 @@ Triggers Dependency Checking =================== -* Flush cached query plans when the dependent objects change, - when the cardinality of parameters changes dramatically, or +* -Flush cached query plans when the dependent objects change or when new ANALYZE statistics are available - - A more complex solution would be to save multiple plans for different - cardinality and use the appropriate plan based on the EXECUTE values. - -* Track dependencies in function bodies and recompile/invalidate - - 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. One complexity is that a function - might itself drop and recreate dependent tables, causing it to - invalidate its own query plan. - -* Invalidate prepared queries, like INSERT, when the table definition +* -Track dependencies in function bodies and recompile/invalidate +* -Invalidate prepared queries, like INSERT, when the table definition is altered diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index e4e5982249..2ed075d4ae 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -2,14 +2,16 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -PostgreSQL TODO List +z -

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sat May 5 10:47:39 EDT 2007 -

z
+PostgreSQL TODO List +

+Current maintainer: Bruce Momjian (bruce@momjian.us)
+Last updated: Sat May 5 11:39:57 EDT 2007 +

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.

@@ -23,7 +25,7 @@ you would like to work on an item, please read the Developer's FAQ
first. There is also a developer's wiki at
http://developer.postgresql.org.

Administration

Allow major upgrades without dump/reload, perhaps using pg_upgrade @@ -151,7 +153,7 @@ first. There is also a developer's wiki at

Monitoring

Allow server log information to be output as INSERT statements @@ -160,7 +162,7 @@ first. There is also a developer's wiki at
-Add ability to monitor the use of temporary sort files

Data Types

-Make 64-bit version of the MONEY data type @@ -298,7 +300,7 @@ first. There is also a developer's wiki at

Functions

Allow INET subnet tests using non-constants to be indexed @@ -354,7 +356,7 @@ first. There is also a developer's wiki at
e.g. box @> point

Multi-Language Support

Add NCHAR (as distinguished from ordinary varchar), @@ -395,7 +397,7 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php

Views / Rules

Automatically create rules on views so they are updateable, per SQL99 @@ -412,7 +414,7 @@ first. There is also a developer's wiki at
are added after the view is created.

SQL Commands

Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT @@ -701,7 +703,7 @@ first. There is also a developer's wiki at

Clients

Have pg_ctl look at PGHOST in case it is a socket directory? @@ -815,7 +817,7 @@ first. There is also a developer's wiki at

Triggers

Add deferred trigger queue file @@ -850,26 +852,16 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php

Dependency Checking

Flush cached query plans when the dependent objects change, - when the cardinality of parameters changes dramatically, or +
-Flush cached query plans when the dependent objects change or when new ANALYZE statistics are available -
A more complex solution would be to save multiple plans for different - cardinality and use the appropriate plan based on the EXECUTE values. -
-
Track dependencies in function bodies and recompile/invalidate -
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. One complexity is that a function - might itself drop and recreate dependent tables, causing it to - invalidate its own query plan. -
-
Invalidate prepared queries, like INSERT, when the table definition +
-Track dependencies in function bodies and recompile/invalidate +
-Invalidate prepared queries, like INSERT, when the table definition is altered

Indexes

Add UNIQUE capability to non-btree indexes @@ -942,7 +934,7 @@ first. There is also a developer's wiki at

Fsync

Improve commit_delay handling to reduce fsync() @@ -960,7 +952,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php

Cache Usage

Allow free-behind capability for large sequential scans, perhaps using @@ -1025,7 +1017,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php

Vacuum

Improve speed with indexes @@ -1095,7 +1087,7 @@ first. There is also a developer's wiki at

Locking

Fix priority ordering of read and write light-weight locks (Neil) @@ -1115,7 +1107,7 @@ first. There is also a developer's wiki at
Add idle_in_transaction_timeout GUC so locks are not held for long periods of time

Startup Time Improvements

Experiment with multi-threaded backend for backend creation [thread] @@ -1138,7 +1130,7 @@ first. There is also a developer's wiki at
existing backends is one of the difficulties with a backend approach.

Write-Ahead Log

Eliminate need to write full pages to WAL before page modification [wal] @@ -1204,7 +1196,7 @@ first. There is also a developer's wiki at
of indexes on TOAST tables.

Optimizer / Executor

Improve selectivity functions for geometric operators @@ -1229,7 +1221,7 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php

Miscellaneous Performance

Do async I/O for faster random read-ahead of data @@ -1274,7 +1266,7 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php

Source Code

Add use of 'const' for variables in source tree @@ -1349,7 +1341,7 @@ first. There is also a developer's wiki at
of result sets using new statement protocol

Exotic Features

Add pre-parsing phase that converts non-ISO syntax to supported @@ -1377,7 +1369,7 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php

Features We Do Not Want

All backends running as threads in a single process (not wanted) -- 2.40.0