Re: Planner selects different execution plans depending on limit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bill Martin <bill(dot)martin(at)communote(dot)com>
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:04:37
Message-ID: 25753.1347545077@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Bill Martin <bill(dot)martin(at)communote(dot)com> writes:
> Ive 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Bill Martin 2012-09-13 14:42:07 Re: Planner selects different execution plans depending on limit
Previous Message Tomas Vondra 2012-09-13 09:39:52 Re: : PostgreSQL Index behavior