From 9e01aaa8bfa4c1684a93dca2ca14a9c8edf3bf9a Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 12 Aug 2004 19:45:24 +0000 Subject: [PATCH] Add: > * Allow finer control over the caching of prepared query plans > > Currently, queries prepared via the libpq API are planned on first > 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. > --- doc/TODO | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/TODO b/doc/TODO index daf84ba00e..83292df8eb 100644 --- a/doc/TODO +++ b/doc/TODO @@ -5,7 +5,7 @@ TODO list for PostgreSQL Bracketed items "[]" have more detail. Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Tue Aug 10 13:30:30 EDT 2004 +Last updated: Thu Aug 12 15:45:17 EDT 2004 The most recent version of this document can be viewed at the PostgreSQL web site, http://www.PostgreSQL.org. @@ -295,6 +295,14 @@ Commands * Allow PREPARE of cursors * Allow PREPARE to automatically determine parameter types based on the SQL statement +* Allow finer control over the caching of prepared query plans + + Currently, queries prepared via the libpq API are planned on first + 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. + * Allow LISTEN/NOTIFY to store info in memory rather than tables? Currently LISTEN/NOTIFY information is stored in pg_listener. Storing -- 2.40.0