| From: | Andrei Gaspar <andi(at)softnrg(dot)dnttm(dot)ro> | 
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Sort and index | 
| Date: | 2005-04-18 15:36:14 | 
| Message-ID: | 4263D3EE.5010409@softnrg.dnttm.ro | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
Hi,
I thought that an index can be used for sorting.
I'm a little confused about the following result:
create index OperationsName on Operations(cOperationName);
explain SELECT * FROM Operations ORDER BY cOperationName;
                              QUERY PLAN
-----------------------------------------------------------------------
 Sort  (cost=185.37..189.20 rows=1532 width=498)
   Sort Key: coperationname
   ->  Seq Scan on operations  (cost=0.00..104.32 rows=1532 width=498)
(3 rows)
Is this supposed to be so?
Andrei
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.15 - Release Date: 4/16/2005
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-04-18 15:43:54 | Re: How to improve db performance with $7K? | 
| Previous Message | Bruno Wolff III | 2005-04-18 15:21:18 | Re: Storing Large Objects |