pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthias Ackermann <matt@webcraft.ch>
To: pgsql-sql@hub.org
Subject: Usage of index in "ORDER BY" operations
Date: Sat, 27 Nov 1999 16:32:15 +0100
Message-ID: <383FF97F.8F408F3B@webcraft.ch> (raw)

I notice following behaviour:

I have a table "adress" with 100'000 adresses 
with columns (last_name, first_name, adressline1, etc.)
and an index last_name_idx on the column "last_name".

The query
"SELECT * FROM adress ORDER BY last_name LIMIT 20 OFFSET 0;"

takes forever and "EXPLAIN" shows that the index on last_name 
is not being used.

On the other hand 

"SELECT * FROM adress WHERE last_name > '' ORDER BY last_name LIMIT 20 OFFSET 0;"

returns the result immediately and "EXPLAIN" shows that the index on
last_name is being used.

So it seems that inserting a WHERE-clause, even if it doesn't do 
anything at all (i.e. doesn't reduce the result-set), 
is necessary to force the DB to make use of the index.

It even says in the FAQ under 4.9) 
"Indexes are not used for ORDER BY operations."

So I was wondering: 
Am I doing something wrong here or is the lesson simply: 
"Include all attributes of an index in a where-clause
if you want the indexes to be used"?

Is there a better way to tell the DB to make use of the index?

BTW: This seems to be true for indexes on multiple columns, i.e.
if having an index on (last_name, first_name) the query had to be:
SELECT * FROM adress WHERE last_name >'' AND first_name >'' 
ORDER BY last_name, first_name LIMIT 20 OFFSET 0;
Omitting the where-clause again leads to a very slow query.

I apologize if this has been discussed many times before ...

Thanks for your help.
Matt



view thread (2+ messages)  latest in thread

Message-ID: <383FF97F.8F408F3B@webcraft.ch>
Permalink:  ../383FF97F.8F408F3B@webcraft.ch/
Also on:    postgresql.org/message-id/383FF97F.8F408F3B@webcraft.ch

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: matt@webcraft.ch, pgsql-sql@hub.org
  Subject: Re: Usage of index in "ORDER BY" operations
  In-Reply-To: <383FF97F.8F408F3B@webcraft.ch>
  References: <383FF97F.8F408F3B@webcraft.ch>

* 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