>
> * Add the ability to automatically create materialized views
>
>   Right now materialized views require the user to create triggers on the
>   main table to keep the summary table current.  SQL syntax should be able
>   to manager the triggers and summary table automatically.  A more
>   sophisticated implementation would automatically retrieve from the
>   summary table when the main table is referenced, if possible.
>
This commit is contained in:
Bruce Momjian 2008-01-14 22:14:30 +00:00
parent be8451e548
commit 1272ac82b6
2 changed files with 18 additions and 2 deletions

View File

@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Fri Jan 11 11:49:17 EST 2008
Last updated: Mon Jan 14 17:13:36 EST 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -432,6 +432,15 @@ Views / Rules
http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php
* Add the ability to automatically create materialized views
Right now materialized views require the user to create triggers on the
main table to keep the summary table current. SQL syntax should be able
to manager the triggers and summary table automatically. A more
sophisticated implementation would automatically retrieve from the
summary table when the main table is referenced, if possible.
SQL Commands
============

View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Fri Jan 11 11:49:17 EST 2008
Last updated: Mon Jan 14 17:13:36 EST 2008
</p>
<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>.
@ -385,6 +385,13 @@ first. There is also a developer's wiki at<br/>
</li><li>Make it possible to use RETURNING together with conditional DO INSTEAD
rules, such as for partitioning setups
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php">http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php</a>
</p>
</li><li>Add the ability to automatically create materialized views
<p> Right now materialized views require the user to create triggers on the
main table to keep the summary table current. SQL syntax should be able
to manager the triggers and summary table automatically. A more
sophisticated implementation would automatically retrieve from the
summary table when the main table is referenced, if possible.
</p>
</li></ul>
<h1><a name="section_7">SQL Commands</a></h1>