Re: GSoC 2011 Eager MV implementation proposal - Mailing list pgsql-hackers

On 03/31/2011 04:38 PM, AAMIR KHAN wrote: <blockquote
cite="mid:AANLkTin6BJVrGpLn-S9ivKT1ZPBDJwX_2v7ZcsWxckD_@mail.gmail.com"type="cite"><span class="Apple-style-span"
style="border-collapse:collapse; font-family: arial,sans-serif;"><div style="background-color: transparent;
font-family:'Times New Roman';"><font size="3"><span style="white-space: pre-wrap;"></span></font><span
style="font-size:12pt; font-family: 'Times New Roman'; color: rgb(0, 0, 0); background-color: transparent; font-weight:
normal;font-style: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">I would like to
implementeager materialized view.An eager materialized view will be updated whenever the view changes. This is done
witha system of triggers on all of the underlying tables.</span><br /></div></span></blockquote><br /> Last summer
someoneworked on snapshot materialized views.  That didn't result in anything that could be committed.  If you wanted
towork on trying to actually finish that, that might go somewhere useful.  There are a number of hard problems in
gettinga working implementation of materialized views that all get ignored by all of the student proposals we get, and
whatyou're talking about doesn't address any of them.<br /><br /> You really should read all of the messages in the
followingthreads:<br /><br /><a class="moz-txt-link-freetext"
href="http://archives.postgresql.org/pgsql-hackers/2010-04/msg00479.php">http://archives.postgresql.org/pgsql-hackers/2010-04/msg00479.php</a><br
/><aclass="moz-txt-link-freetext"
href="http://archives.postgresql.org/pgsql-hackers/2010-06/msg00743.php">http://archives.postgresql.org/pgsql-hackers/2010-06/msg00743.php</a><br
/><aclass="moz-txt-link-freetext"
href="http://archives.postgresql.org/pgsql-hackers/2010-07/msg00396.php">http://archives.postgresql.org/pgsql-hackers/2010-07/msg00396.php</a><br
/><br/> And the following summaries:<br /><br /><a class="moz-txt-link-freetext"
href="http://wiki.postgresql.org/wiki/Materialized_Views_GSoC_2010">http://wiki.postgresql.org/wiki/Materialized_Views_GSoC_2010</a><br
/><aclass="moz-txt-link-freetext"
href="http://rhaas.blogspot.com/2010/04/materialized-views-in-postgresql.html">http://rhaas.blogspot.com/2010/04/materialized-views-in-postgresql.html</a><br
/><br/> And then say how what you're suggesting fits into the issues raised last summer.  The theory and way to
implementeager MVs are interesting problems.  But working on them won't lead toward code that can be committed to
PostgreSQLthis year.<br /><br /><pre class="moz-signature" cols="72">-- 
 
Greg Smith   2ndQuadrant US    <a class="moz-txt-link-abbreviated"
href="mailto:greg@2ndQuadrant.com">greg@2ndQuadrant.com</a>  Baltimore, MD
 
PostgreSQL Training, Services, and 24x7 Support  <a class="moz-txt-link-abbreviated"
href="http://www.2ndQuadrant.us">www.2ndQuadrant.us</a>

</pre>