| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | decibel <decibel(at)decibel(dot)org> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-general(at)postgresql(dot)org, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: contrib/plantuner - enable PostgreSQL planner hints |
| Date: | 2009-10-17 01:38:58 |
| Message-ID: | 407d949e0910161838x3229b2edq57f144a34fcfc16@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, Oct 16, 2009 at 10:04 AM, decibel <decibel(at)decibel(dot)org> wrote:
> Out of curiosity, did you look at doing hints as comments in a query? I'm
> guessing you couldn't actually do that in just a contrib module, but it's
> how Oracle handles hints, and it seems to be *much* more convenient, because
> a hint only applies for a specific query
Fwiw Oracle is moving away from this now. At OpenWorld the optimizer
folks were pleading with folks to get rid of all their hard-coded
hints by preparing plans for hinted queries and loading those as the
approved plans. In 11g there's a system which ensures the database
will not run any plan that isn't approved.
In fact it looks an *awful* lot like the system I sketched out 6 years
ago in: http://article.gmane.org/gmane.comp.db.postgresql.devel.general/11385
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | decibel | 2009-10-17 03:51:43 | Re: Inheritance on foreign key |
| Previous Message | Kirk Wythers | 2009-10-17 00:11:11 | Re: db not dumping properly, or at least not restoring |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2009-10-17 04:28:54 | Re: Reworks for Access Control facilities (r2363) |
| Previous Message | Greg Stark | 2009-10-17 01:23:12 | Re: Deprecation |