On Sun, Mar 28, 2010 at 10:01 PM, gaurav gupta <gauravkumar.gu...@students.iiit.ac.in> wrote: > My idea is to add a functionality of Auto tuning and Auto Indexing/ > Reindexing in DB languages. > > Though I am not working on this I have some idea about implementation. > Idea is that on the no. of rows deleted, Inserted in the table we can make > our system capable to reindex the table that will save the time of user.
Reindexing is not routine maintenance for PostgreSQL, so this seems fairly pointless. > Similarly using the no. of select hits on a table we can check that if > maximum no. of times it is on a non-index field we can index on that field > to make select faster. Well, a SELECT statement "hits" a whole row, not a single column; but even if you could somehow figure out a way to tally up per-column statistics (and it's certainly not obvious to me how to do such a thing) it doesn't follow that a column which is frequently accessed is a good candidate for indexing. I don't think this is a good project for a first-time hacker, or something that can realistically be completed in one summer. It sounds more like a PhD project to me. I wrote to another student who is considering submitting a GSOC proposal with some ideas I thought might be suitable. You might want to review that email: http://archives.postgresql.org/pgsql-hackers/2010-03/msg01034.php ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
