| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Searching for the cause of a bad plan |
| Date: | 2007-09-21 15:48:09 |
| Message-ID: | 1190389689.4661.220.camel@PCD12478 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> OK, I can confirm that. I set the statistics target for column "a" on
> table_a to 1000, analyzed, and got the plan below. The only downside is
> that analyze became quite expensive on table_a, it took 15 minutes and
> touched half of the pages... I will experiment with lower settings,
> maybe it will work with less than 1000 too.
So, just to finish this up: setting statistics to 100 worked too, and it
has an acceptable impact on analyze. My original (more complicated)
query is working fine now, with visible effects on server load...
Thanks Simon for your help !
Cheers,
Csaba.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-21 16:08:33 | Re: Searching for the cause of a bad plan |
| Previous Message | Denes Daniel | 2007-09-21 15:36:25 | Query planner unaware of possibly best plan |