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

From Grzegorz Jaśkiewicz
Subject Re: LIMIT causes planner to do Index Scan using a less optimal index
Date
Msg-id q2s2f4958ff1004070612ha4e21200uf29a00f9b1747968@mail.gmail.com
Whole thread Raw
In response to Re: LIMIT causes planner to do Index Scan using a less optimal index  (Sherry.CTR.Zhu@faa.gov)
Responses Re: LIMIT causes planner to do Index Scan using a less optimal index  (Sherry.CTR.Zhu@faa.gov)
List pgsql-performance


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: Sherry.CTR.Zhu@faa.gov
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
Next
From: Sherry.CTR.Zhu@faa.gov
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index