Re: Is unique index always used if query is on first constituent column ? - Mailing list pgsql-admin

From Tom Lane
Subject Re: Is unique index always used if query is on first constituent column ?
Date
Msg-id 13436.1167502010@sss.pgh.pa.us
Whole thread Raw
In response to Re: Is unique index always used if query is on first constituent column ?  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-admin
Bruno Wolff III <bruno@wolff.to> writes:
>   Rajesh Kumar Mallah <mallah.rajesh@gmail.com> wrote:
>> create unique index ab on t(a,b);
>> create index b on t(b);

> If the b data is large you might get some performance increase from adding
> an index on just a. You will be trading off increased work when doing updates
> to handle the extra index versus faster searches in a more compact index.

This is covered in some detail in TFM:
http://www.postgresql.org/docs/8.2/static/indexes-multicolumn.html
http://www.postgresql.org/docs/8.2/static/indexes-bitmap-scans.html

            regards, tom lane

pgsql-admin by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: Is unique index always used if query is on first constituent column ?
Next
From: "Shahryar G. Hashemi"
Date:
Subject: pg_restore: [archiver (db)] could not execute query: ERROR: zero-length delimited identifier at or near """" at character 60