I created the index, in order. Did a vacuum analyze on the table and my
explain still says:
Limit (cost=229610.78..229611.03 rows=100 width=717)
-> Sort (cost=229610.78..230132.37 rows=208636 width=717)
Sort Key: receipt, carrier_id, batchnum, encounternum, encounter_id
-> Seq Scan on detail_summary ds (cost=0.00..22647.13 rows=208636
width=717)
Filter: (receipt >= '2004-03-22'::date)
So, for fun I did
set enable_seqscan to off
But that didn't help. For some reason, the sort wants to do a seq scan and
not use my super new index.
Am I doing something wrong ?
----- Original Message -----
From: "Josh Berkus" <josh@xxxxxxxxxxxx>
To: <pgsql-performance@xxxxxxxxxxxxxx>
Cc: <J@xxxxxxxxxxx>
Sent: Tuesday, January 17, 2006 5:25 PM
Subject: Re: [PERFORM] Multiple Order By Criteria
J,
I have an index built for each of these columns in my order by clause.
This query takes an unacceptable amount of time to execute. Here are the
results of the explain:
You need a single index which has all five columns, in order.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
