pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Valentine Gogichashvili <valgog@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Cannot make GIN intarray index be used by the planner
Date: Wed, 9 May 2007 15:12:45 +0200
Message-ID: <3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com> (raw)

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

view thread (6+ messages)  latest in thread

Message-ID: <3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com>
Permalink:  ../3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com/
Also on:    postgresql.org/message-id/3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: valgog@gmail.com
  Subject: Re: Cannot make GIN intarray index be used by the planner
  In-Reply-To: <3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox