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

Re: GSoC Query

From: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: gaurav gupta <gauravkumar(dot)gupta(at)students(dot)iiit(dot)ac(dot)in>, xzilla(at)users(dot)sourceforge(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: GSoC Query
Date: 2010-03-29 10:42:08
Message-ID: 9362e74e1003290342i645d27a7sa7fd21b417432b56@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
>
>
>
>  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.
>>
>
> It's impractical to figure out where indexes should go at without
> simulating what the optimizer would then do with them against a sample set
> of queries.  You can't do anything useful just with basic statistics about
> the tables.
>
> I would recommend
> http://msdn.microsoft.com/en-us/library/aa226167(SQL.70).aspx<http://msdn.microsoft.com/en-us/library/aa226167%28SQL.70%29.aspx>as a good, practical introduction to the topic of what it takes to figure
> out where indexes go at, from someone who came up with a reasonable solution
> to that problem.  You can find a list of the underlying research they cite
> (and an idea what has been done since then) at
> http://portal.acm.org/citation.cfm?id=673646
>
>
Even if you have devised a way to find the appropriate set of indexes, just
have a index adviser, which would advise a set of indexes for a set of
queries and let the DBA and the application user take the final call, after
looking at them..

Gokul.

In response to

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2010-03-29 11:16:11
Subject: Re: Known Issues Page
Previous:From: Takahiro ItagakiDate: 2010-03-29 09:47:05
Subject: Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC

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