Re: Determining which index to create

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Eric Cholet <cholet(at)logilune(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Determining which index to create
Date: 2001-11-22 01:21:12
Message-ID: 20011122122112.A2666@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 21, 2001 at 04:09:52PM +0100, Eric Cholet wrote:
> => explain select * from dico_frs where motid=4742 order by date desc limit
> 10;
> NOTICE: QUERY PLAN:
>
> Limit (cost=46172.25..46172.25 rows=10 width=16)
> -> Sort (cost=46172.25..46172.25 rows=11382 width=16)
> -> Index Scan using dico_frs_motid_date on dico_frs
> (cost=0.00..45405.39 rows=11382 width=16)

That's wrong. It doesn't seem to realise that a reverse scan on the index
would give the right answer. Note that that's only true because you're
selecting only a single motid. If there were multiple, a reverse scan would
definitly not be appropriate.

Not sure how to fix this though.

Functional index?
--
Martijn van Oosterhout <kleptog(at)svana(dot)org>
http://svana.org/kleptog/
> Magnetism, electricity and motion are like a three-for-two special offer:
> if you have two of them, the third one comes free.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dado Feigenblatt 2001-11-22 01:32:06 backup: pg_dumpall and full backups in general
Previous Message Bruce Momjian 2001-11-22 00:49:14 Re: TOAST performance (was Re: [GENERAL] Delete Performance)