Skip site navigation (1) Skip section navigation (2)

Re: GSoC Query

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: gaurav gupta <gauravkumar(dot)gupta(at)students(dot)iiit(dot)ac(dot)in>
Cc: xzilla(at)users(dot)sourceforge(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: GSoC Query
Date: 2010-03-29 02:52:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Mar 28, 2010 at 10:01 PM, gaurav gupta
<gauravkumar(dot)gupta(at)students(dot)iiit(dot)ac(dot)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:


In response to

  • GSoC Query at 2010-03-29 02:01:45 from gaurav gupta

pgsql-hackers by date

Next:From: Joseph AdamsDate: 2010-03-29 03:24:22
Subject: Re: Proposal: Add JSON support
Previous:From: gaurav guptaDate: 2010-03-29 02:01:45
Subject: GSoC Query

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group