From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Index Tuning Features |
Date: | 2006-10-11 05:44:30 |
Message-ID: | c2d9e70e0610102244n11e7407etebb813b2ddfe698d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/10/06, Mark Woodward <pgsql(at)mohawksoft(dot)com> wrote:
> I think the idea of "virtual indexes" is pretty interesting, but
> ultimately a lesser solution to a more fundimental issue, and that would
> be "hands on" control over the planner. Estimating the effect of an index
> on a query "prior" to creating the index is a great idea, how that is done
> is something different than building concensus that it should be done.
>
> Another thing that this brings up is "hints" to a query. Over the years, I
> have run into situation where the planner wasn't great. It would be nice
> to try forcing different strategies on the planner and see if performance
> caan be improved.
>
you can do this by setting enable_"access_method" type parameters.
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
From | Date | Subject | |
---|---|---|---|
Next Message | George Pavlov | 2006-10-11 06:44:56 | query log corrupted-looking entries |
Previous Message | Richard Broersma Jr | 2006-10-11 05:31:47 | Re: left outer join on multi tables |