pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John A Meinel <john@arbash-meinel.com>
To: Yves Vindevogel <yves.vindevogel@implements.be>
Cc: pgsql-performance@postgresql.org
Subject: Re: Limit clause not using index
Date: Tue, 21 Jun 2005 09:42:36 -0500
Message-ID: <42B8275C.8040300@arbash-meinel.com> (raw)
In-Reply-To: <d0da86521cd54473cac40df63bb14546@implements.be>
References: <d0da86521cd54473cac40df63bb14546@implements.be>

Yves Vindevogel wrote:

> Hi,
>
> I have a very simple query on a big table. When I issue a "limit" 
> and/or "offset" clause, the query is not using the index.
> Can anyone explain me this ?

You didn't give enough information. What does you index look like that 
you are expecting it to use?
Generally, you want to have matching columns. So you would want
CREATE INDEX blah ON tblprintjobs(loginuser, desceventdate, desceventtime);

Next, you should post EXPLAIN ANALYZE instead of regular explain, so we 
can have an idea if the planner is actually making correct estimations.

John
=:->

>
> rvponp=# explain select * from tblprintjobs order by loginuser, 
> desceventdate, desceventtime offset 25 limit 25 ;
> QUERY PLAN
> ----------------------------------------------------------------------------------- 
>
> Limit (cost=349860.62..349860.68 rows=25 width=206)
> -> Sort (cost=349860.56..351416.15 rows=622236 width=206)
> Sort Key: loginuser, desceventdate, desceventtime
> -> Seq Scan on tblprintjobs (cost=0.00..25589.36 rows=622236 width=206)
> (4 rows)
>
> rvponp=# explain select * from tblprintjobs order by loginuser, 
> desceventdate, desceventtime ;
> QUERY PLAN
> ----------------------------------------------------------------------------- 
>
> Sort (cost=349860.56..351416.15 rows=622236 width=206)
> Sort Key: loginuser, desceventdate, desceventtime
> -> Seq Scan on tblprintjobs (cost=0.00..25589.36 rows=622236 width=206)
> (3 rows)
>
> Met vriendelijke groeten,
> Bien à vous,
> Kind regards,
>
> *Yves Vindevogel*
> *Implements*

Attachments:

  signature.asc (application/pgp-signature, 252B) download

view thread (14+ messages)  latest in thread

Message-ID: <42B8275C.8040300@arbash-meinel.com>
Permalink:  ../42B8275C.8040300@arbash-meinel.com/
Also on:    postgresql.org/message-id/42B8275C.8040300@arbash-meinel.com

 · 

reply

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: john@arbash-meinel.com, yves.vindevogel@implements.be
  Subject: Re: Limit clause not using index
  In-Reply-To: <42B8275C.8040300@arbash-meinel.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