Re: Cannot make GIN intarray index be used by the planner - Mailing list pgsql-performance

From Oleg Bartunov
Subject Re: Cannot make GIN intarray index be used by the planner
Date
Msg-id Pine.LNX.4.64.0705091728560.12152@sn.sai.msu.ru
Whole thread Raw
In response to Cannot make GIN intarray index be used by the planner  ("Valentine Gogichashvili" <valgog@gmail.com>)
Responses Re: Cannot make GIN intarray index be used by the planner  ("Valentine Gogichashvili" <valgog@gmail.com>)
List pgsql-performance
Do you have both indexes (GiST, GIN) on the same table ?

On Wed, 9 May 2007, Valentine Gogichashvili wrote:

> Hello all,
>
> I am trying to move from GiST intarray index to GIN intarray index, but my
> GIN index is not being used by the planner.
>
> The normal query is like that
>
> select *
> from sourcetablewith_int4
> where ARRAY[myint] <@ myint_array
>  and some_other_filters
>
> (with GiST index everything works fine, but GIN index is not being used)
>
> If I create the same table populating it with text[] data like
>
> select myint_array::text[] as myint_array_as_textarray
> into newtablewith_text
> from sourcetablewith_int4
>
> and then create a GIN index using this new text[] column
>
> the planner starts to use the index and queries run with grate speed when
> the query looks like that:
>
> select *
> from newtablewith_text
> where ARRAY['myint'] <@ myint_array_as_textarray
>  and some_other_filters
>
> Where the problem can be with _int4 GIN index in this constellation?
>
> by now the enable_seqscan is set to off in the configuration.
>
> With best regards,
>
> -- Valentine Gogichashvili
>

     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

pgsql-performance by date:

Previous
From: Andrzej Zawadzki
Date:
Subject: Poor performance with queries using clause: sth IN (...)
Next
From: "Valentine Gogichashvili"
Date:
Subject: Re: Cannot make GIN intarray index be used by the planner