| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-performance(at)postgresql(dot)org, Denis Lussier <denisl(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, "korryd(at)enterprisedb(dot)com" <korryd(at)enterprisedb(dot)com>, "Jonah H(dot) Harris" <jharris(at)enterprisedb(dot)com>, "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Subject: | Re: Simple join optimized badly? |
| Date: | 2006-10-09 20:30:59 |
| Message-ID: | 1160425859.6181.18.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, 2006-10-08 at 18:05, Josh Berkus wrote:
> Now, if you were offering us a patch to auto-populate the statistics as a
> table is loaded, I'd be all for that. But I, personally, would need a
> lot of convincing to believe that hints don't do more harm than good.
Actually, I'd much rather have a log option, on by default, that spit
out info messages when the planner made a guess that was off by a factor
of 20 or 50 or so or more on a plan.
I can remember to run stats, but finding slow queries that are slow
because the plan was bad, that's the hard part.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-09 21:18:27 | Re: Simple join optimized badly? |
| Previous Message | Steinar H. Gunderson | 2006-10-09 18:45:04 | Re: odd variances in count(*) times |