Re: BUG #4351: Full text search performance - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4351: Full text search performance
Date
Msg-id 23257.1218504639@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4351: Full text search performance  ("Lawrence Cohan" <Lawrencec@1shoppingcart.com>)
Responses Re: BUG #4351: Full text search performance
List pgsql-bugs
"Lawrence Cohan" <Lawrencec@1shoppingcart.com> writes:
> -- Is there anything wrong in the sequence below? Sory but I couldn't figure
> it out by myself from FAQ or from the internet.

> --Added FT indexes as documented for product_name and long_description
> CREATE INDEX idx_ft_products_long_description ON products USING
> gin(to_tsvector('english', long_description));
> CREATE INDEX idx_ft_products_name ON products USING
> gin(to_tsvector('english', product_name));
> analyze products;

> --tried the FT queries below:
> EXPLAIN
> SELECT product_name FROM products
> WHERE to_tsvector(product_name) @@ to_tsquery('album');

That query isn't going to match that index.  You'd need to write

... WHERE to_tsvector('english', product_name) @@ to_tsquery('album');

Basically, you can't rely on a default TS configuration when using the
functional-index approach to text searching, because of the restriction
that index contents can't depend on mutable state.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Treat
Date:
Subject: return query with set-returning functions
Next
From: Tom Lane
Date:
Subject: Re: return query with set-returning functions