| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Mladen Gogala <mgogala(at)vmsinfo(dot)com> |
| Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5652: Optimizer does wrong thing with partitioned tables |
| Date: | 2010-09-10 19:00:20 |
| Message-ID: | 1284145220.21706.7.camel@jdavis-ux.asterdata.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 2010-09-10 at 10:37 -0400, Mladen Gogala wrote:
> Euler, optimizer is selecting a wrong path, which is a bug by
> definition.
I agree that the optimizer should be improved here, but it's not really
a "bug". I think what you are requesting is considered more of a feature
to make the optimizer smarter.
The optimizer will never be so good that it always picks the best path.
Consider a 100-table join: would it be a "bug" if it didn't find the
perfect join order?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2010-09-10 19:09:10 | Re: BUG #5652: Optimizer does wrong thing with partitioned tables |
| Previous Message | Chris Travers | 2010-09-10 15:10:15 | Re: BUG #5652: Optimizer does wrong thing with partitioned tables |