| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Overriding the optimizer |
| Date: | 2005-12-16 03:20:28 |
| Message-ID: | 43A2327C.8000206@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> ... This seems like a case where PostgreSQL's current optimiser should
>> easily know what to do if your config settings are correct and you've
>> been running ANALYZE, so I'd like to see your settings and the explain
>> analyze plan...
>
> I could, but it would divert us from the main topic of this discussion.
> It's not about that query, which was just an example. It's the larger
> issue.
So your main example bad query is possibly just a case of lack of
analyze stats and wrong postgresql.conf config? And that's what causes
you to shut down your database? Don't you want your problem FIXED?
But like I said - no developer is interested in doing planner hints.
Possibly you could get a company to sponsor it. Maybe what you want is
a statement of "If someone submits a good, working, fully implemented
patch that does planner hints, then we'll accept it."
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig A. James | 2005-12-16 03:38:36 | Re: Overriding the optimizer |
| Previous Message | Mark Kirkwood | 2005-12-16 03:16:58 | Re: Overriding the optimizer |