Re: sequential scan unduly favored over text search gin index

From: Sushant Sinha <sushant354(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: sequential scan unduly favored over text search gin index
Date: 2011-06-20 16:04:00
Message-ID: 1308585840.2488.13.camel@dragflick
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Mon, 2011-06-20 at 10:58 -0500, Kevin Grittner wrote:
> 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?
Yes and I mentioned that the row estimates are correct, which indicate
that the problem is somewhere else.

-Sushant.

> -Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Vladimir Kulev 2011-06-20 16:08:00 Re: Inoptimal query plan for max() and multicolumn index
Previous Message Kevin Grittner 2011-06-20 15:58:13 Re: sequential scan unduly favored over text search gin index