| From: | Bill Martin <bill(dot)martin(at)communote(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Planner selects different execution plans depending on limit |
| Date: | 2012-09-13 14:42:07 |
| Message-ID: | D48BF41C96B16442B542F5E25C259047011E80F02A@COM211.communardo.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-performance |
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Bill Martin <bill(dot)martin(at)communote(dot)com> writes:
>> I've tried different values for the statistics but it is all the same (the planner decide to switch to a seqscan if the limit is 10).
>> ALTER TABLE core_content ALTER column content SET STATISTICS 1000;
> Um, did you actually do an ANALYZE after changing that?
>
> regards, tom lane
Yes, I've run the ANALYZE command.
Regards,
Bill Martin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Krogh | 2012-09-13 14:48:07 | Re: Planner selects different execution plans depending on limit |
| Previous Message | Sebastien FLAESCH | 2012-09-13 13:10:23 | Re: Details about libpq cross-version compatibility |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Krogh | 2012-09-13 14:48:07 | Re: Planner selects different execution plans depending on limit |
| Previous Message | Tom Lane | 2012-09-13 14:04:37 | Re: Planner selects different execution plans depending on limit |