Re: difference between a unique constraint and a unique index ??? - Mailing list pgsql-performance

From Dave Cramer
Subject Re: difference between a unique constraint and a unique index ???
Date
Msg-id 694A5959-73AC-4C18-AA5F-489407A6CFDC@fastcrypt.com
Whole thread Raw
In response to Re: difference between a unique constraint and a unique index ???  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On 12-Nov-07, at 11:37 AM, Tom Lane wrote:

> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>> Well, AFAIK the index with varchar_pattern_ops is used for LIKE
>> queries,
>> whereas the other one is going to be used for = queries.  So you
>> need to
>> keep both indexes.
>
> Given the current definition of text equality, it'd be possible to
> drop
> ~=~ and have the standard = operator holding the place of equality in
> both the regular and pattern_ops opclasses.  Then it'd be possible to
> support regular equality queries, as well as LIKE, with only the
> pattern_ops index.
>
That would be ideal. Having two indexes on the same column isn't
optimal.

Dave

pgsql-performance by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Need to run CLUSTER to keep performance
Next
From: Stephane Bailliez
Date:
Subject: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table