Re: Slow fulltext query plan - Mailing list pgsql-performance

From Tom Lane
Subject Re: Slow fulltext query plan
Date
Msg-id 772.1334366203@sss.pgh.pa.us
Whole thread Raw
In response to Re: Slow fulltext query plan  (Benoit Delbosc <bdelbosc@nuxeo.com>)
List pgsql-performance
Benoit Delbosc <bdelbosc@nuxeo.com> writes:
> On 13/04/2012 00:25, Tom Lane wrote:
>> Is there a reason why you're writing the query in such a
>> non-straightforward way, rather than just
>>
>> EXPLAIN ANALYZE SELECT hierarchy.id
>> FROM hierarchy
>> JOIN fulltext ON fulltext.id = hierarchy.id
>> WHERE (TO_TSQUERY('whatever') @@ nx_to_tsvector(fulltext.fulltext))
>> OR (TO_TSQUERY('whatever') @@ nx_to_tsvector(fulltext.fulltext_title));

> This query is written by a framework, also I thought that is a common
> pattern that can be found in the documentation:
>    http://www.postgresql.org/docs/9.1/interactive/textsearch-controls.html

Well, "common pattern" would be stretching it.  Anyway I've concluded
that this is in fact a planner bug.  There will be a fix in 9.2, but I'm
not going to take the risk of back-patching it, so you might want to
think about changing that framework.

            regards, tom lane

pgsql-performance by date:

Previous
From: Claudio Freire
Date:
Subject: Re: scale up (postgresql vs mssql)
Next
From: Filippos
Date:
Subject: Re: bad planning with 75% effective_cache_size