Skip site navigation (1) Skip section navigation (2)

Re: sequential scan unduly favored over text search gin index

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <sushant354(at)gmail(dot)com>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: sequential scan unduly favored over text search gin index
Date: 2011-06-20 15:58:13
Message-ID: 4DFF27C5020000250003E9A4@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
Sushant Sinha <sushant354(at)gmail(dot)com> wrote:
 
> I have a tsvector column docvector and a gin index on it
> docmeta1_docvector_idx
> 
> I have a simple query "select * from docmeta1 where docvector @@
> plainto_tsquery('english', 'free');" 
> 
> I find that the planner chooses a sequential scan of the table
> even when the index performs orders of magnitude.
 
Did you ANALYZE the table after loading the data and building the
index?
 
-Kevin

In response to

Responses

pgsql-performance by date

Next:From: Sushant SinhaDate: 2011-06-20 16:04:00
Subject: Re: sequential scan unduly favored over text search gin index
Previous:From: Jon NelsonDate: 2011-06-20 15:53:52
Subject: bad plan: 8.4.8, hashagg, work_mem=1MB.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group