Re: are there any method that "Update" command not affect other unrelated indices?

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: sunpeng <bluevaley(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: are there any method that "Update" command not affect other unrelated indices?
Date: 2010-10-13 06:52:33
Message-ID: FA1370A2-6C7A-4FCB-A1C8-F2715E5568C0@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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't expect 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!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message 勝俣 智成 2010-10-13 06:57:38 about RPM build options
Previous Message Alban Hertroys 2010-10-13 06:38:19 Re: are there any method that "Update" command not affect other unrelated indices?