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

Re: Queryplan within FTS/GIN index -search.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: jesper(at)krogh(dot)cc, pgsql-performance(at)postgresql(dot)org
Subject: Re: Queryplan within FTS/GIN index -search.
Date: 2009-10-23 15:51:11
Message-ID: 1256313071.2580.800.camel@jdavis (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Fri, 2009-10-23 at 09:26 +0100, Richard Huxton wrote:
> That structure isn't exposed to the planner though, so it doesn't
> benefit from any re-ordering the planner would normally do for normal
> (exposed) AND/OR clauses.

I don't think that explains it, because in the second plan you only see
a single index scan with two quals:

   Index Cond: ((ftsbody_body_fts @@
     to_tsquery('commonterm'::text)) AND (ftsbody_body_fts @@

So it's entirely up to GIN how to execute that.

	Jeff Davis

In response to


pgsql-performance by date

Next:From: Grzegorz JaƛkiewiczDate: 2009-10-23 15:56:36
Subject: Re: query planning different in plpgsql?
Previous:From: Scott MeadDate: 2009-10-23 15:49:50
Subject: Re: query planning different in plpgsql?

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