Skip to content

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

Update based on user comments: 

<   in PL/PgSQL is to use EXECUTE.
>   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.
parent bdfa8e5e
Hide whitespace changes
Inline Side-by-side
Showing with 8 additions and 4 deletions
doc/TODO
View file @ cad7f831
...@@ -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: Fri Aug 26 15:10:29 EDT 2005 Last updated: Fri Aug 26 15:32:39 EDT 2005
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.
...@@ -621,7 +621,9 @@ Dependency Checking ...@@ -621,7 +621,9 @@ Dependency Checking
This is particularly important for references to temporary tables This is particularly important for references to temporary tables
in PL/PgSQL because PL/PgSQL caches query plans. The only workaround in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
in PL/PgSQL is to use EXECUTE. 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.
Exotic Features Exotic Features
......
doc/src/FAQ/TODO.html
View file @ cad7f831
...@@ -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: Fri Aug 26 15:10:29 EDT 2005 Last updated: Fri Aug 26 15:32:39 EDT 2005
</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>.
...@@ -563,7 +563,9 @@ first. ...@@ -563,7 +563,9 @@ first.
</li><li>Track dependencies in function bodies and recompile/invalidate </li><li>Track dependencies in function bodies and recompile/invalidate
<p> This is particularly important for references to temporary tables <p> This is particularly important for references to temporary tables
in PL/PgSQL because PL/PgSQL caches query plans. The only workaround in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
in PL/PgSQL is to use EXECUTE. 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.
</p> </p>
</li></ul> </li></ul>
<h1><a name="section_12">Exotic Features</a></h1> <h1><a name="section_12">Exotic Features</a></h1>
......
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