From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Michael McFarland <sidlonDoesntLikeSpam@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: adding 'limit' leads to very slow query
Date: Mon, 7 Mar 2005 23:03:43 -0800 (PST)
Message-ID: <20050307230123.L97147@megazone.bigpanda.com> (raw)
In-Reply-To: <opsnaj0hctsvs6tg@localhost.localdomain>
References: <opsnaj0hctsvs6tg@localhost.localdomain>
On Mon, 7 Mar 2005, Michael McFarland wrote:
> I'm trying to understand why a particular query is slow, and it seems
> like the optimizer is choosing a strange plan. See this summary:
>
>
> * I have a large table, with an index on the primary key 'id' and on a
> field 'foo'.
> > select count(*) from foo;
> 1,000,000
> > select count(*) from foo where bar = 41;
> 7
>
> * This query happens very quickly.
> > explain select * from foo where barId = 412 order by id desc;
> Sort ()
> Sort key= id
> -> Index scan using bar_index on foo ()
> Index cond: barId = 412
>
> But this query takes forever
>
> > explain select * from foo where barId = 412 order by id desc limit 25;
> Limit ()
> -> Index scan backward using primarykey_index
> Filter: barID = 412
You didn't show the row estimates, but I'd guess that it's expecting
either that ther are more rows that match barId=412 than there actually
are (which may be solvable by raising the statistics target on the column
and re-analyzing) such that going backwards on id in order to make 25
matching rows isn't a bad plan or that barId and id are correlated which
is unfortunately not going to be recognized right now.
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: sszabo@megazone.bigpanda.com, sidlonDoesntLikeSpam@yahoo.com
Subject: Re: adding 'limit' leads to very slow query
In-Reply-To: <20050307230123.L97147@megazone.bigpanda.com>
* 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