Postgres Pro
Downloads
Home   >   mailing lists

Re: LIMIT causes planner to do Index Scan using a less optimal index - Mailing list pgsql-performance

From Sherry.CTR.Zhu@faa.gov
Subject Re: LIMIT causes planner to do Index Scan using a less optimal index
Date
Msg-id OFCDCC668F.8735D136-ON852576FE.00496440-852576FE.004980E3@faa.gov
Whole thread Raw
In response to Re: LIMIT causes planner to do Index Scan using a less optimal index  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Responses Re: LIMIT causes planner to do Index Scan using a less optimal index
List pgsql-performance
Tree view

Please just let me know if Postgres can do this kind of index or not.  

create index idx1 on tb1(col1, col2)

Then later we can find it is useful or useless.  


Thanks much!

Xuefeng Zhu (Sherry)
Crown Consulting Inc. -- Oracle DBA
AIM Lab Data Team
(703) 925-3192



Grzegorz Jaśkiewicz <gryzman@gmail.com>
Sent by: pgsql-performance-owner@postgresql.org

04/07/2010 09:12 AM

To
Sherry CTR Zhu/AWA/CNTR/FAA@FAA
cc
Joel Jacobson <joel@gluefinance.com>, pgsql-performance@postgresql.org, Robert Haas <robertmhaas@gmail.com>
Subject
Re: [PERFORM] LIMIT causes planner to do Index Scan using a less         optimal index







2010/4/7 <Sherry.CTR.Zhu@faa.gov>

Do you mean one index on two columns?

something like this:   create index idx1 on tb1(col1, col2);
yup :) It would be quite useless without that feature.
Don't listen to oracle folks, they obviously know not much about products others than oracle db(s).
 




--
GJ

pgsql-performance by date:

Previous
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
Next
From: Matthew Wakeling
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index