| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Nathan Boley <npboley(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: estimating # of distinct values |
| Date: | 2011-01-20 02:37:56 |
| Message-ID: | AANLkTi=B90S8Whyk5KN13wJw1gqJ3UzSiJiQCHhYAONa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 19, 2011 at 9:35 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
> Also, in my personal experience this isn't really the area we've got
> problems now. The problem cases for me always were queries with a rather
> large number of joins (7 to 10 or so) plus rather complex search
> conditions. The join order, not the access strategy, then becomes the
> deciding factor in plan performance.
This certainly matches my experience (except sometimes with more joins).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-01-20 02:44:32 | Re: ALTER TABLE ... REPLACE WITH |
| Previous Message | Robert Haas | 2011-01-20 02:36:30 | Re: estimating # of distinct values |