Re: multicolumn index column order - Mailing list pgsql-performance

From valgog
Subject Re: multicolumn index column order
Date
Msg-id 1185352440.504985.282370@19g2000hsx.googlegroups.com
Whole thread Raw
In response to Re: multicolumn index column order  ("Valentine Gogichashvili" <valgog@gmail.com>)
Responses Re: multicolumn index column order  (Lew <lew@lewscanon.nospam>)
List pgsql-performance
On Jul 25, 2:14 am, Lew <l...@lewscanon.nospam> wrote:
>
> How about two indexes, one on each column?  Then the indexes will cooperate
> when combined in a WHERE clause.
> <http://www.postgresql.org/docs/8.2/interactive/indexes-bitmap-scans.html>
>
> I don't believe the index makes a semantic difference with regard to ascending
> or descending.  An index is used to locate records in the selection phase of a
> query or modification command.
>
> --
> Lew

Ordered indexes (b-tree in this case) are also used to get the needed
record order and it is absolutely not necessary to have a WHARE clause
in your select statement to use them when you are using ORDER BY.

--
Valentine


pgsql-performance by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Performance issue with 8.2.3 - "C" application
Next
From: Dave Page
Date:
Subject: Re: Table Statistics with pgAdmin III