| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Jaime Casanova" <systemguards(at)gmail(dot)com>, "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 08:21:46 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579016A057C@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
No, not generally. Usual problems include join order and wrong index,
not only wrong access method.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Kelly | 2006-10-11 08:22:34 | Re: more anti-postgresql FUD |
| Previous Message | Zdenek Kotala | 2006-10-11 08:15:22 | Re: Clarification needed |