GSoC 2011 Eager MV implementation proposal

Title: Implementation of Eager Materialized views in postgres

Name of Proposer & Email : Aamir Khan & ak4u2009(at)gmail(dot)com

Synopsis:

I would like to implement eager materialized view.An eager materialized view
will be updated whenever the view changes. This is done with a system of
triggers on all of the underlying tables.

Benefits to the PostgreSQL Community:
First of all, it would be the best if my work is helpful to everybody who
misses materialized views in PostgreSQL, because PostgreSQL do not have
still implemented materialized views. In addition, MV is mentioned as the
top rated feature in TODO list.

Deliverables:
First of all, at the end of whole my project is not only finishing the
patch if possible, get patch into next PostgreSQL release, or keep git
repository actual to last PosgreSQL version.
Bio

I am student of one of the most premier institute in India namely Indian
Institute of Technology Roorkee pursuing my Bachelor of Technology Computer
Science & Engineering.

I, as a part of team manages institutes website www.iitr.ac.in . We have
setup a intranet portal inside campus of IIT Rookee which has around 80
applications hosted on it. I have created ebooks sharing portal within the
intranet. I have very good experience in web designing (e.g, I have created
website during last year summer internship www.raysconsultants.com ).
Regarding open source work : i have submitted many patches for phpmyadmin

I like to contribute in open source communitites because it gives me
experience,technical expertise and it teaches spirit of team work. And its
my time to give back to community from which i gained a lot of experience
and motivation.

Project plan

I am completely free this summer. I intend to indulge in some of my hobbies
this summer, like Squash etc, leaving me plenty of time to complete my
project. The tentative schedule as discussed with my mentor is :

(1) Identify how an eager MV system would work, by labelling and
identifying every table, query, trigger, etc... This would be a
written document that has been checked by me for completeness,
precision, and correctness. (1 week)

(2) Identify the internal structure of a parsed query, the basic
atomic parts of this structure, and how each atomic structure maps
precisely to our MV system described in (1). Again, a written document
approved by myself, and reviewed by the PostgreSQL community. (2
weeks)

(3) Outline how a "create_eager_mv" function would work, starting with
the interface (what parameters it takes), and working through the
exact SQL commands that must be executed to complete the process.
Identify which SQL commands depend on the structure of the query. (2
weeks)

(4) Write unit tests that check a variety of queries against your (as
of yet, unwritten) function. Ensure completeness by reviewing with me.
(1 week)

(5) Finally, given all of the above, translate (3) into working code,
likely implemented in PL/Python or C, that passes the unit tests.
Submit to PostgreSQL community for review. (2 weeks)

Contact Information

Name: Aamir Khan
Country: Indian
School and degree: Indian Institute of Technology, Roorkee, Bachelor of
Technology
Email: ak4u2009(at)gmail(dot)com
Phone: +91-9557647357