From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bill Martin <bill.martin@communote.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Planner selects different execution plans depending on limit
Date: Thu, 13 Sep 2012 10:04:37 -0400
Message-ID: <25753.1347545077@sss.pgh.pa.us> (raw)
In-Reply-To: <D48BF41C96B16442B542F5E25C259047011E80EBB4@COM211.communardo.local>
References: <D48BF41C96B16442B542F5E25C259047011E80EBB4@COM211.communardo.local>
Bill Martin <bill.martin@communote.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, bill.martin@communote.com
Subject: Re: Planner selects different execution plans depending on limit
In-Reply-To: <25753.1347545077@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox