Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
Cannot make GIN intarray index be used by the planner - Mailing list pgsql-performance
From
Valentine Gogichashvili
Subject
Cannot make GIN intarray index be used by the planner
Date
May 9, 2007
10:13:34
Msg-id
3ce9822f0705090612nd6198a2xd06da85f1accbae9@mail.gmail.com
Whole thread
Raw
Responses
Re: Cannot make GIN intarray index be used by the planner
List
pgsql-performance
Tree view
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
i
s set to off in the configuration.
With best regards,
-- Valentine Gogichashvili
pgsql-performance
by date:
Previous
From:
Peter Eisentraut
Date:
09 May 2007, 09:11:07
Subject:
Apparently useless bitmap scans
Next
From:
Andrzej Zawadzki
Date:
09 May 2007, 10:29:29
Subject:
Poor performance with queries using clause: sth IN (...)
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies