Re: LIMIT causes planner to do Index Scan using a less optimal index

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Sherry.CTR.Zhu@xxxxxxx
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
From: Grzegorz Jaśkiewicz <gryzman@xxxxxxxxx>
Date: Wed, 7 Apr 2010 14:12:35 +0100
Cc: Joel Jacobson <joel@xxxxxxxxxxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx, Robert Haas <robertmhaas@xxxxxxxxx>
In-reply-to: <OFB0E54E57.8291629B-ON852576FE.0048251D-852576FE.0048332D@xxxxxxx>
References: <o2l2f4958ff1004070551o30fe9871g17fe164a5fdd36af@xxxxxxxxxxxxxx> <OFB0E54E57.8291629B-ON852576FE.0048251D-852576FE.0048332D@xxxxxxx>

2010/4/7 <Sherry.CTR.Zhu@xxxxxxx>

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

Follow-Ups:
- Re: LIMIT causes planner to do Index Scan using a less optimal index
  - From: Sherry . CTR . Zhu

References:
- Re: LIMIT causes planner to do Index Scan using a less optimal index
  - From: Grzegorz Jaśkiewicz
- Re: LIMIT causes planner to do Index Scan using a less optimal index
  - From: Sherry . CTR . Zhu

Prev by Date: Re: LIMIT causes planner to do Index Scan using a less optimal index
Next by Date: Re: LIMIT causes planner to do Index Scan using a less optimal index
Previous by thread: Re: LIMIT causes planner to do Index Scan using a less optimal index
Next by thread: Re: LIMIT causes planner to do Index Scan using a less optimal index
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux