From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Ken Williams <ken(at)mathforum(dot)org> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Problem with indexes, LIMIT, ORDER BY ... DESC |
Date: | 2002-06-07 16:41:06 |
Message-ID: | 20020607093917.C37907-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 7 Jun 2002, Ken Williams wrote:
> ==========================================================================
> =
> announce=# explain select date from foo where date < '06/08/2001
> 23:59' and code = 'FOO' order by code, date DESC limit 1;
> NOTICE: QUERY PLAN:
>
> Limit (cost=24397.98..24397.98 rows=1 width=20)
> -> Sort (cost=24397.98..24397.98 rows=6355 width=20)
> -> Index Scan using foo_code_date on foo
> (cost=0.00..23996.55 rows=6355 width=20)
> ==========================================================================
> =
>
> What can I do to improve this?
I'd suggest trying: order by code DESC, date DESC.
Otherwise the index order and sort order aren't exactly alike. In this
case there's only one code value so we can see that it shouldn't matter
but I doubt the optimizer knows that.
From | Date | Subject | |
---|---|---|---|
Next Message | M.L.Bowman | 2002-06-07 16:47:21 | deny table creation |
Previous Message | Bruce Momjian | 2002-06-07 16:30:53 | Re: psql -l gives bad output |