Skip to content

P
Postgres FD Implementation
Commit 80aa37a7 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Add: 

> * Invalidate prepared queries, like INSERT, when the table definition
>   is altered
parent e747f493
Hide whitespace changes
Inline Side-by-side
Showing with 6 additions and 2 deletions
doc/TODO
View file @ 80aa37a7
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Tue Apr 25 22:15:17 EDT 2006 Last updated: Wed Apr 26 22:41:35 EDT 2006
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -398,6 +398,8 @@ SQL Commands ...@@ -398,6 +398,8 @@ SQL Commands
manually or automatically when statistics for execute parameters manually or automatically when statistics for execute parameters
differ dramatically from those used during planning. differ dramatically from those used during planning.
* Invalidate prepared queries, like INSERT, when the table definition
is altered
* Allow LISTEN/NOTIFY to store info in memory rather than tables? * Allow LISTEN/NOTIFY to store info in memory rather than tables?
Currently LISTEN/NOTIFY information is stored in pg_listener. Storing Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
......
doc/src/FAQ/TODO.html
View file @ 80aa37a7
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Tue Apr 25 22:15:17 EDT 2006 Last updated: Wed Apr 26 22:41:35 EDT 2006
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -368,6 +368,8 @@ first. ...@@ -368,6 +368,8 @@ first.
manually or automatically when statistics for execute parameters manually or automatically when statistics for execute parameters
differ dramatically from those used during planning. differ dramatically from those used during planning.
</p> </p>
</li><li>Invalidate prepared queries, like INSERT, when the table definition
is altered
</li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables? </li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
<p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing <p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
such information in memory would improve performance. such information in memory would improve performance.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment