Re: are there any method that "Update" command not affect other unrelated indices? - Mailing list pgsql-general

From Alban Hertroys
Subject Re: are there any method that "Update" command not affect other unrelated indices?
Date
Msg-id FA1370A2-6C7A-4FCB-A1C8-F2715E5568C0@solfertje.student.utwente.nl
Whole thread Raw
In response to are there any method that "Update" command not affect other unrelated indices?  (sunpeng <bluevaley@gmail.com>)
List pgsql-general
On 13 Oct 2010, at 24:03, sunpeng wrote:

> Hi, I have the following table:
> CREATE TABLE A
> (
>    a1 integer not null,
>    a2 integer,
>    a3 integer,
>    a4 integer
> )
> and have the following four indices:
> create index ind_a1 on A USING gist(a1);
> create index ind_a2 on A USING gist(a2);
> create index ind_a3 on A USING gist(a3);
> create index ind_a4 on A USING gist(a4);


Is there any reason you're using gist indices on integer fields? Those are primarily used with full-text searching, I
wouldn'texpect them to be particularly efficient for scalar values. A (default) btree would probably perform better. 

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,4cb55736678302085914008!



pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: are there any method that "Update" command not affect other unrelated indices?
Next
From: 勝俣 智成
Date:
Subject: about RPM build options